v3.0.0 — explicit MCP discovery and anonymous client contracts

okama-mcp 3.0.0

Breaking changes since 2.0.0

• Client identity intake through MCP is removed: client_create is absent and
  install-skill no longer installs the retired AI intake workflow. A human
  enters names and contacts through Planner's local intake instead.
• Client updates accept only the documented safe fields; names, contacts,
  arbitrary notes and private paths are not part of the MCP contract.
• Household forecasts and client/report integrations require the anonymous-data
  interface okama_planner.ai. Reports require a valid privacy proof and return
  an opaque artifact basename; legacy private branding files are not read.

These changes were already present on main after 2.0.0. They make this a major
release even though the discovery additions preserve valid core JSON inputs.

New and improved

• Complete nested input schemas for portfolios, efficient frontiers, financial
  plans, Monte Carlo, all five cash-flow strategies and chart inputs.
• Exact symbol/ticker/ISIN and name matches rank ahead of other search hits.
  Namespace catalogs support offset, has_more and next_offset; filtering
  and ordering happen before pagination. Scoped punctuation is literal.
• Namespace capability metadata and actionable RATE/INFL/RATIO corrections.
• Planner/client descriptions and schemas support English, Russian, German,
  Spanish and Chinese when a compatible companion enables those integrations.

Fixed

• Nominal asset returns with inflation disabled no longer access real-return
  properties; real_mean_return is null. Requesting real returns while disabling
  inflation produces a readable input correction.
• Macro series sent to asset tools point to the appropriate macro tool without
  substituting a different financial series. Unexpected backend errors stay masked.

Compatibility and known limitations

Standard installations currently resolve Planner 0.4.1, which does not contain
okama_planner.ai. They expose 50 core tools; household Planner, local-client
and report integrations remain unavailable until a compatible companion release.
This is tracked in #6.
The development privacy suite uses the public Planner source commit pinned in CI;
this does not mean the published dependency has the same capabilities. The core
finplan_* tools remain available through okama itself.

Restrictive frontier weight bounds remain affected by
okama#132. MCP does not relax them.
Rebalancing may emit pandas compatibility warnings tracked in
okama#133.

Upgrade and verification

Use uvx --refresh --from okama-mcp==3.0.0 okama-mcp stdio, or upgrade an existing
Poetry installation with poetry add okama-mcp@3.0.0. Restart the MCP client so it
reloads the tool schemas. Self-hosted HTTP uses the same package; mcp.okama.io
serves the landing page and has no public MCP endpoint.

The original user scenarios, test results and manual checklist are in
discovery validation. Reporter-specific
model comparisons remain pending the model and MCP-client specifications.