1236 go-to-market products and 3,080 of their individual MCP tools, drawn by one measurement nobody else publishes: not whether a vendor says it has an MCP server, but whether an agent can actually reach it and what it finds when it does. Search a product, a tool name, or a job. Click any chip for the full picture.
Solid: the recorded URL answered an MCP initialize on 2026-09-04, with a control probe confirming the 401 was not a blanket auth wall. Hatched: a repository or package; callable after an install, not a remote endpoint. Grey: the vendor's page about the server, not the server; the server may exist somewhere the directory does not record. This is liveness, not quality. Nobody has run these.
Conversation Intel is 37 percent officially MCP'd. Enablement & Coaching is 3 percent. AI SDRs, the category whose whole pitch is agents, sit at 5 percent with 1 server answering a handshake. The tools built for agents are the hardest for agents to use.
Every tool name came from the server itself (a live tools/list), its source code, or the vendor's documentation, and each carries which. read, write or spend is derived from the tool's own name and description. A tool being listed is not a test that it works; bench_tested is a separate and much rarer claim.