{
 "url": "https://agenticweb.wiki/compare/anp-vs-mcp/",
 "title": "Agent Network Protocol vs Model Context Protocol",
 "description": "Agent Network Protocol vs Model Context Protocol: The map lists them as complementary: sites and agents commonly implement both. Side-by-side step…",
 "markdown_url": "https://agenticweb.wiki/compare/anp-vs-mcp/index.md",
 "markdown": "# Agent Network Protocol (ANP) vs Model Context Protocol (MCP)\n\nThe map lists them as complementary: sites and agents commonly implement both. They answer different questions: Agent Network Protocol is a step 6 (Coordinate) standard, Model Context Protocol step 5 (Act), so they are not substitutes.\n\n[6 Coordinate](/category/coordinate/) [Agent Network Protocol](/protocols/anp/) · [5 Act](/category/act/) [Model Context Protocol](/protocols/mcp/)\n\n|  | [Agent Network Protocol](/protocols/anp/) ANP | [Model Context Protocol](/protocols/mcp/) MCP |\n| --- | --- | --- |\n| Lifecycle step | 6 Coordinate: Talk to another agent | 5 Act: Do something for me |\n| Answers | How can decentralized agents from different platforms authenticate, discover, and message each other without a central registry? | How does an AI application call tools and pull structured context, prompts, and data from an external server? |\n| Governed by | Community-led open-source project (agent-network-protocol GitHub org) | Agentic AI Foundation (Linux Foundation umbrella); day-to-day spec work in the modelcontextprotocol GitHub org via public SEPs (Specification Enhancement Proposals) and working groups |\n| Status (issuer's words) | Released v1.2 (core suite); meta-protocol (ANP-06) remains draft/unreleased | Active open specification, current dated release 2026-07-28 |\n| Version | v1.2 (2026-09-24) | 2026-07-28 (2026-07-28) |\n| Form / transport | well-known file | endpoint |\n| Found at | /.well-known/agent-descriptions | GET {endpoint}/server-card (SEP-2127 Final, application/mcp-server-card+json, discovered via /.well-known/ai-catalog.json; /.well-known/mcp.json is legacy SEP-1649) |\n| Implementation | shipping | multi-implementation — Three independent registry censuses, kept separate and not averaged. VerifyMCP as of 2026-10-19 (https://verifymcp.io/stats, embedded in <script id=\"stats-charts-data\"> time-series JSON; HTML hero card reflects latest daily snapshot): 47,870 logical servers (45,953 active, 601 deprecated, 1,316 deleted; 31,337 remote; 30,842 Streamable HTTP; among handshook components, 20,031 on 2025-11-25 and 6,571 on 2026-07-28). Registry Discussion 1580 as of 2026-08-27 (https://github.com/modelcontextprotocol/registry/discussions/1580): a cursor walk of 82,994 version records yielding 25,125 distinct isLatest servers across 15,468 publishers (13,279 Streamable HTTP remotes). Registry Discussion 1548 as of 2026-08-19 (https://github.com/modelcontextprotocol/registry/discussions/1548): 22,636 active latest registrations (12,077 declaring an HTTPS remote). |\n| Evidence | 3 verified | 11 verified, 2 reported |\n| Primary use case | Let agents talk to other agents | Expose tools to agents |\n| Last verified | 2026-10-23 (current) | 2026-10-23 (current) |\n| Specification | [https://github.com/agent-network-protocol/AgentNetworkProtocol](https://github.com/agent-network-protocol/AgentNetworkProtocol) | [https://modelcontextprotocol.io/specification/2026-07-28/index](https://modelcontextprotocol.io/specification/2026-07-28/index) |\n\n## When to use which\n\n- Choose Agent Network Protocol when your question is “How can decentralized agents from different platforms authenticate, discover, and message each other without a central registry?” and you accept its maturity: status \"Released v1.2 (core suite); meta-protocol (ANP-06) remains draft/unreleased\", implementation shipping.\n- Choose Model Context Protocol when your question is “How does an AI application call tools and pull structured context, prompts, and data from an external server?” and you accept its maturity: status \"Active open specification, current dated release 2026-07-28\", implementation multi-implementation (Three independent registry censuses, kept separate and not averaged. VerifyMCP as of 2026-10-19 (https://verifymcp.io/stats, embedded in <script id=\"stats-charts-data\"> time-series JSON; HTML hero card reflects latest daily snapshot): 47,870 logical servers (45,953 active, 601 deprecated, 1,316 deleted; 31,337 remote; 30,842 Streamable HTTP; among handshook components, 20,031 on 2025-11-25 and 6,571 on 2026-07-28). Registry Discussion 1580 as of 2026-08-27 (https://github.com/modelcontextprotocol/registry/discussions/1580): a cursor walk of 82,994 version records yielding 25,125 distinct isLatest servers across 15,468 publishers (13,279 Streamable HTTP remotes). Registry Discussion 1548 as of 2026-08-19 (https://github.com/modelcontextprotocol/registry/discussions/1548): 22,636 active latest registrations (12,077 declaring an HTTPS remote).).\n\nGuidance is derived from the two records (question, status, implementation, prerequisites, pairings), not from opinion. Each record's page carries its numbered references.\n\n## Read the full articles\n\n- [Agent Network Protocol](/protocols/anp/): How can decentralized agents from different platforms authenticate, discover, and message each other without a central registry?\n- [Model Context Protocol](/protocols/mcp/): How does an AI application call tools and pull structured context, prompts, and data from an external server?\n\nAsk the MCP server to compare any two: the compare-protocols prompt, or get on both ids. [Connect](/connect/).\n\n[anp.json](/data/protocols/anp.json) · [mcp.json](/data/protocols/mcp.json) · [Markdown](/compare/anp-vs-mcp/index.md)\n"
}