MCP’s July specification gives wallet-data integrations a new compatibility checklist

The Model Context Protocol maintainers released specification version 2026-07-28 on 28 July. Its core moves to stateless requests, removes the protocol-level initialization handshake and session identifiers, and introduces server/discover for capability and version discovery. The release announcement and changelog are linked below; this article examines what those changes mean for wallet research.

Compatibility is more than a connector URL

Our analysis: an AI client and a data server need to agree on the protocol version, supported capabilities and the format of results. A configuration copied from an older setup guide may be insufficient. Before trusting a connector, ask whether its maintainer names the supported version and publishes a working example for that version.

The changelog also introduces freshness and cache-scope fields for resource and catalog responses. Those protocol hints describe how a result may be cached. They do not establish when an exchange position was observed. A research answer still needs the original data timestamp and a clear distinction between current state and historical observations.

A practical check for wallet research

• Verify that the client and server support a common MCP revision.
• Check that a result identifies its wallet, network, observation time and any unavailable fields.
• Ask the agent to attach source URLs to its interpretation so a reader can inspect the evidence.
• Review the documented permissions before allowing any account-specific operation.

WalletFollow’s Data API is available. Its native MCP connector remains planned, so this protocol release should not be read as a WalletFollow connector launch. Reading public wallet information and authorizing copy trading are distinct workflows; a language model’s recommendation supplies neither account consent nor execution authority.