Contract 1.7.0 · Local previewRead Markdown

Versioning and changelog

Contract version

The current operation contract is 1.7.0. get_account_context returns contract_version; errors include it too. The operation contract version is separate from the MCP transport protocol version.

Compatibility and deprecation

Change Version bump
Description, title, or documentation wording that does not change behavior patch
New tool, new optional input field, new output field, or new error code minor
Raised limit, or a relaxed input constraint minor
New required input field, removed or renamed field, changed field type or meaning major
Removed tool, lowered limit, new required scope, or stricter input constraint major
Renaming a published tool: the new name is added and the old one deprecated minor
Removing a deprecated tool or a renamed tool’s old name major
  • Clients must ignore output fields they do not recognize; minor versions can add them.
  • Clients must treat unknown error codes by their retryable flag.
  • A tool is deprecated for at least one minor release before a major release removes it. A rename keeps the old name working, marked deprecated, until that major release.

Changelog

1.0.0 · October 18, 2026 · Local implementation

Sixteen tools, three data scopes, OAuth code flow with PKCE, CIMD and DCR, consent, Connected apps, bounded reads, guarded writes and replay receipts. The local Inspector and SDK test suites verify the implementation. Hosted deployment, live client acceptance, legal approval and directory publication remain pending.

Transport compatibility

The implementation uses official MCP server/client SDK 2.3.1 with modern 2026-07-28 and documented legacy negotiation. Cadence does not implement MCP Apps widgets, prompts or resources. Refresh cached tool metadata after a reviewed server change.