A2A Agent Card · Model Context Protocol (MCP)

Model Context Protocol

Near-conformant. Correctly shaped against the A2A 1.0.0 AgentCard object, but omits optional fields an agent may expect.
Provider: Model Context Protocol (MCP) Conformance: Near-Conformant Protocol: 0.3 Transport: HTTP+JSON Version: 1.0.0 Host: modelcontextprotocol.io Skills: 2
Discovery

An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.

https://modelcontextprotocol.io/.well-known/agent-card.json
Interfaces
https://modelcontextprotocol.io/ · transport · protocol non-standard supportedInterfaces
Skills (2)

draft-sep

Research and draft a Specification Enhancement Proposal following the MCP SEP governance process

search-mcp-github

Search MCP PRs, issues, and discussions across the modelcontextprotocol GitHub org

Documentation
https://modelcontextprotocol.io/
Evidence. Fetched 2026-07-28 from https://modelcontextprotocol.io/.well-known/agent-card.json, HTTP 200. The body was saved verbatim and is the sole source for everything on this page — no field is inferred. View the captured card. Providers change what they serve; if this card has moved or changed shape, the provider profile carries the current state as of the last build.