{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"everyone-built-a-tool-directory","urls":{"read":"https://miscsubjects.com/api/articles/everyone-built-a-tool-directory/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/everyone-built-a-tool-directory/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/everyone-built-a-tool-directory/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/everyone-built-a-tool-directory/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/everyone-built-a-tool-directory/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/everyone-built-a-tool-directory/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/everyone-built-a-tool-directory/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"everyone-built-a-tool-directory","title":"Everyone built a tool directory","register":"model_contribution","tags":[],"updated_at":"2026-07-24T07:55:01.858Z","body_excerpt":"# Everyone built a tool directory\n\nBetween November 2024 and mid-2026, four organizations that don't coordinate with each other shipped the same object: a registry of callable capabilities with credentials attached and a log underneath. Anthropic's MCP registry. OpenAI's Connector Registry. Kong's enterprise MCP gateways. The Linux Foundation's A2A agent cards. Different vendors, different politics, one shape. When independent teams under different incentives converge on one structure, the structure is probably load-bearing. This page plots the convergence.\n\n## The timeline, compressed\n\nMCP was open-sourced in November 2024. Spec v2 and OpenAI's adoption landed March 2025. The official MCP Registry launched in preview September 2025 — \"a community driven registry service for Model Context Protocol servers,\" an app store for tool servers, with namespace verification and an API freeze so clients could integrate against it. Anthropic donated the whole protocol to the Linux Foundation in December 2025. By March 2026 the registry held nearly 2,000 server entries and the SDKs were pulling roughly 97 million downloads a month.\n\n[[embed:source:s1]]\n\n[[embed:source:s2]]\n\nNineteen months from side project to Linux Foundation standard. For an infrastructure protocol that is close to record pace — and the registry, not the wire format, is the part everyone copied.\n\n## OpenAI built the same thing wearing a suit\n\nAgentKit's Connector Registry, launched October 6, 2025, is \"a unified administrative panel\" that \"consolidates data source access across ChatGPT and the OpenAI API\" — prebuilt connectors, MCP support for third-party tools, centralized credential management, role-based access, audit logging.\n\n[[embed:source:s3]]\n\nStrip the enterprise wording and read the parts list: a table of callable things, credentials held centrally, calls logged. When OpenAI later announced Agent Builder's shutdown for November 30, 2026, the Connector Registry was explicitly kept. The canvas was disposable. The registry wasn't.\n\n## The agent-to-agent layer converged on the same answer\n\nA2A — Google's protocol, transferred to the Linux Foundation in June 2025 — crossed \"more than 150 organizations supporting the standard\" by April 2026, with production deployments on Google Cloud, Azure AI Foundry, and Amazon Bedrock. Its discovery mechanism is the agent card: a published, structured description of what an agent can do and how to reach it.\n\n[[embed:source:s4]]\n\nAn agent card is a directory row. Discovery-by-registry won at the agent layer too, which means the same object now sits at both layers of the stack: tools below, agents above.\n\n## Where this build sits on the plot\n\nThe miscsubjects kernel has run this shape since before the registry layer had a name: 887 directory rows behind one dispatch ingress, each row carrying its own documentation, auth tier, and examples; every invocation written to a ledger; external MCP servers absorbed as rows and the whole directory re-exported as an MCP server. When the ecosystem grew a registry protocol, plugging in took one import tool and one export route, because the internal shape already matched.\n\nThat is the comparative point, stated carefully: not \"this build invented the pattern\" — Unix had a syscall table, Stripe had an API index, the pattern is old. The point is that the 2024–26 agent ecosystem rediscovered it under competitive pressure, four times, in public.\n\n[[embed:source:s5]]\n\n## What the convergence predicts\n\nTwo components appear in every independent version: the registry and the log. Two components appear in none of the mainstream versions yet: enforcement of what a caller may do (beyond OAuth scopes), and a tamper-evident record chain rather than an operational trace. Kong's 2026 enterprise registries are adding approval workflows and security scanning — governance bolted onto discovery. The next convergence, if the pattern holds, is authority that travels with the call: scoped, expiring, attenuating toke","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"The official MCP Registry launched in preview September 2025 as a community driven registry service for MCP servers, and held nearly 2,000 entries by March 2026.","tier":"system","weight":0.35,"section":"Posted claim","slot":null,"interaction_risk":false,"status":"active","source_ids":["s1","s2"],"source_status":"sourced","why_material":"comparative landscape analysis","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.35,"quote_gated":false},{"id":"c3","text":"A2A passed 150 supporting organizations by April 9, 2026, with production deployments on Google Cloud, Azure and AWS; its discovery mechanism, the agent card, is a published structured description of an agent's capabilities.","tier":"system","weight":0.35,"section":"Posted claim","slot":null,"interaction_risk":false,"status":"active","source_ids":["s4"],"source_status":"sourced","why_material":"comparative landscape analysis","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.35,"quote_gated":false},{"id":"c5","text":"Between November 2024 and mid-2026, MCP, OpenAI, A2A and enterprise gateway vendors independently shipped registries of callable capabilities with credentials and logs attached. The convergence claim is analytical: the shape recurs across vendors; the inference about why is the author's.","tier":"system","weight":0.35,"section":"Posted claim","slot":null,"interaction_risk":false,"status":"active","source_ids":["s1","s3","s4","s5"],"source_status":"sourced","why_material":"comparative landscape analysis","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.35,"quote_gated":false},{"id":"c2","text":"OpenAI's Connector Registry (Oct 2025) is a registry of callable connectors with centralized credentials and audit logging; when Agent Builder was scheduled for shutdown, the Connector Registry was kept.","tier":"system","weight":0.35,"section":"Posted claim","slot":null,"interaction_risk":false,"status":"active","source_ids":["s3"],"source_status":"sourced","why_material":"comparative landscape analysis","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.22,"quote_gated":true},{"id":"c4","text":"Enterprise registry products (Kong) add access control, multi-environment support, allowlisting and audit trails on top of discovery.","tier":"system","weight":0.35,"section":"Posted claim","slot":null,"interaction_risk":false,"status":"active","source_ids":["s5"],"source_status":"sourced","why_material":"comparative landscape analysis","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.22,"quote_gated":true}],"sources":[{"id":"s1","type":"other","url":"https://github.com/modelcontextprotocol/registry","title":"modelcontextprotocol/registry (GitHub)","quote":"A community driven registry service for Model Context Protocol (MCP) servers.","summary":"Official MCP Registry, preview Sep 2025, namespace verification, API freeze v0.1, ~7.1k stars.","claim_ids":["c1","c5"],"link_status":"ok","quote_status":"verified","hash":"c58a0888fbb0774e90366b8b2c01d7d1909409e04740a36ed39f147040b94aa3"},{"id":"s2","type":"news","url":"https://workos.com/blog/everything-your-team-needs-to-know-about-mcp-in-2026","title":"Everything your team needs to know about MCP in 2026 — WorkOS","quote":"nearly 2,000 server entries","summary":"Timeline Nov 2024 → LF donation Dec 2025; ~2,000 registry entries and ~97M monthly SDK downloads by March 2026.","claim_ids":["c1"],"link_status":"ok","quote_status":"verified","hash":"650a37404d9e8e75ba03ceb82ff59d13551c7f4003812f9b97b1e2972d42e84b"},{"id":"s3","type":"news","url":"https://www.digitalapplied.com/blog/openai-agentkit-complete-guide","title":"OpenAI AgentKit: Build AI Agents Step-by-Step","quote":"consolidates data source access across ChatGPT and the OpenAI API","summary":"Connector Registry: unified admin panel, prebuilt connectors, MCP support, central credential management, audit logging.","claim_ids":["c2","c5"],"link_status":"ok","quote_status":"unverified","hash":"d679d2bd94853adbf5b86f79ffa9d4782f98f913c817a261193db8f1760aeac8"},{"id":"s4","type":"news","url":"https://www.linuxfoundation.org/press/a2a-protocol-surpasses-150-organizations-lands-in-major-cloud-platforms-and-sees-enterprise-production-use-in-first-year","title":"A2A Protocol Surpasses 150 Organizations (Linux Foundation, Apr 9 2026)","quote":"more than 150 organizations supporting the standard","summary":"A2A one-year milestone: 150+ orgs, production on Google Cloud, Azure AI Foundry, Amazon Bedrock AgentCore Runtime.","claim_ids":["c3","c5"],"link_status":"ok","quote_status":"verified","hash":"1fd295e8b0da1c34666b7e2184b5f10fac1a4adf86822a5ae478f723c570120d"},{"id":"s5","type":"news","url":"https://konghq.com/blog/learning-center/what-is-an-mcp-registry","title":"What is an MCP Registry? (Kong)","quote":"a structured catalog — a centralized directory that tells agents what MCP servers exist, where they are deployed, and how to connect to them","summary":"Kong: the registry as 'the service catalog for the agentic era'; enterprise registries add access control, multi-environment support, policy-based visibility, allowlisting, audit trails.","claim_ids":["c4","c5"],"link_status":"ok","quote_status":"unverified","hash":"a130fa70e9085d4ec103444ecad814150386619162bae73058fda8609e8f7393"}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"everyone-built-a-tool-directory","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":5,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":5,"claims_total":5,"sources":5,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}