Orbit: Agent communication and tooling
MCP (Model Context Protocol)
An open JSON-RPC protocol that lets LLM applications connect to servers that offer tools, resources and prompts.
- Steward
- Agentic AI Foundation (AAIF), a Linux Foundation directed fund formed 2025-12-09, with Anthropic contributing MCP
- Status
- Live
- Primary source
- Model Context Protocol Specification, version 2025-11-25 (external link)
What it is
standardizes how an AI application talks to a server that offers . The client usually lives inside a chat product or coding , and the server exposes tools the client can call, resources it can read and prompts it can insert. Messages are JSON-RPC 2.0 between hosts, clients and servers, carried over stdio or Streamable HTTP. Source [1]
Status
is live and uses dated specification revisions; the atlas reads revision 2025-11-25. Source [1] On 2025-12-09 the Linux Foundation announced the (AAIF), with Anthropic contributing MCP alongside Block’s goose and OpenAI’s AGENTS.md. The founding platinum members were Amazon Web Services, Anthropic, Block, Bloomberg, Cloudflare, Google, Microsoft and OpenAI. Source [2]
How it relates to the eight
For agentic payments is the plumbing that other rails ride on. Several of the eight define how their messages travel inside MCP calls.
- x402 defines an MCP transport: a tool result with
isError: truecarries thePaymentRequireddata, the client retries with payment in_meta["x402/payment"], and settlement comes back in_meta["x402/payment-response"]. Source [3] The project publishes an@x402/mcppackage. Source [4] - MPP has a draft JSON-RPC and MCP transport for its Payment authentication , with advertisement and payment data placed in MCP’s
_meta. Source [5] - ACP added an MCP in its 2026-04-17 release; its OpenRPC file defines MCP tools that map one to one to the REST checkout operations, with authentication handled at the MCP server level. Source [6, 7, 8]
- UCP lists MCP as a transport with an OpenRPC schema, specifies Streamable HTTP rather than SSE, and applies the same signature rules to MCP POST requests. Source [9, 10]
- ERC-8004 registration files accept an
MCPservice entry with endpoint and version, and feedback entries may name an MCP tool, prompt or resource. Source [11] - AP2 samples run merchant, credentials provider and payment processor roles as MCP servers, and the AP2 FAQ says an SDK and an MCP server are being worked on. Source [12, 13, 14]
- For Visa TAP, Visa publishes MCP client and token manager packages for its Intelligent Commerce APIs; itself does not depend on MCP. Source [15, 16]
- For Mastercard Agent Pay, Mastercard ships the
@mastercard/developers-mcpserver package, which is a general developer tool rather than an Pay component. Source [17]
Status history
- 2025-11-25: specification revision 2025-11-25 released. Source [1]
- 2025-12-09: joins the under the Linux Foundation. Source [2]
Relations at a glance
| Protocol | Relation | Note |
|---|---|---|
| x402 | Complements | x402 defines an MCP transport (payment required in a tool result, payment and settlement carried in _meta) and ships an @x402/mcp package. |
| Stripe MPP (Machine Payments Protocol) | Complements | The MPP specs repository defines a JSON-RPC and MCP transport for the Payment authentication scheme. |
| Agentic Commerce Protocol (ACP) | Complements | The 2026-04-17 ACP release added an MCP transport binding whose tools map to the REST checkout operations. |
| UCP | Complements | UCP lists MCP as a transport, specifies Streamable HTTP for it and signs MCP requests with the same RFC 9421 rules. |
| ERC-8004: Trustless Agents | Compatible with | ERC-8004 registration files accept an MCP service entry, and feedback can reference an MCP tool, prompt or resource. |
| AP2 | Compatible with | AP2 samples run merchant, credentials provider and processor roles as MCP servers; the AP2 FAQ says an SDK and MCP server are being worked on. |
| Visa Trusted Agent Protocol | Compatible with | Visa publishes MCP server and client packages for its Intelligent Commerce APIs; TAP itself does not depend on MCP. |
| Mastercard Agent Pay | Compatible with | Mastercard ships a Developers MCP server package; it is not specific to Agent Pay. |
Sources
- Model Context Protocol Specification, version 2025-11-25 (external link)
- Linux Foundation Announces the Formation of the Agentic AI Foundation (AAIF), Anchored by New Project Contributions Including Model Context Protocol (MCP), goose and AGENTS.md (external link)
- x402 MCP transport (V2) (external link)
- npm downloads API (last month) for x402 packages (external link)
- Payment Authentication Scheme: JSON-RPC and MCP Transport (draft-payment-transport-mcp-00) (external link)
- ACP changelog, version 2026-04-17 (external link)
- MCP Transport Binding for Agentic Checkout (external link)
- ACP OpenRPC schema for the MCP binding, 2026-04-17 (external link)
- UCP Shopping Service MCP OpenRPC (v2026-08-25) (external link)
- UCP Message Signatures (v2026-08-25) (external link)
- ERC-8004: Trustless Agents (specification source, ERCS/erc-8004.md) (external link)
- AP2 repository (README, METADATA, LICENSE) at e1ea56d (external link)
- AP2 repository x402 samples (external link)
- AP2 FAQ (external link)
- visa/ai (formerly visa/mcp) repository: VIC MCP and API clients, vic-agent demo, skills (external link)
- Visa advances agentic commerce with MCP Server, Acceptance Agent Toolkit (external link)
- npm registry: @mastercard/developers-mcp (external link)