MCP’s August roadmap puts agent identity on the wallet-research agenda

On 22 August, the MCP maintainers published an updated roadmap with five priority areas: agentic messaging, HTTP transport, agent identity and security, improved primitives, and SDK developer experience. It describes work after the July specification release. A roadmap identifies intended work; it does not mean that every capability is already standardized or supported by every client.

Why identity matters for crypto data

Our analysis: an agent answering a question from public wallet data has a different permission boundary from an agent accessing a user’s account or requesting a trading action. A future connector should state which identity it recognizes, what access that identity grants, and how the user can revoke that access. A wallet address in a question is an identifier, not proof that the user controls the wallet.

The roadmap’s identity work discusses narrower delegated authority for agents. It also describes progressive discovery to reduce the burden of large tool catalogs. For a wallet-analysis interface, a small set of clearly described research tools can be easier to evaluate than a large catalog whose data and action tools are difficult to distinguish.

Questions for a future integration

• Does a tool read public information, read private account information, or request an action?
• Which permission is required, and can it be revoked independently of wallet ownership?
• Can an answer retain the source wallet, observation time and calculation basis?
• Does the documentation distinguish a released feature from roadmap work?

WalletFollow currently publishes its Data API documentation and public research guides. The native MCP connector is planned. This distinction will stay explicit in our setup documentation so readers can assess what they can use today without confusing protocol progress with a product release.