# By MCP status: every GTM tool sorted by MCP server status

> The one column nobody else publishes. Can an agent call this tool at all, and who built the thing it calls.

*Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).*

---
[Directory](../index.md) / By MCP status

**View: by mcp status**

## The one column nobody else publishes. Can an agent call this tool at all, and who built the thing it calls.

Buckets are the vocabulary in the source markdown, normalised by the build and never invented. The counts below sum to 293 and are reconciled against tools_recount.py.

- [Official MCP](official.md) - 144 of 293 entries. The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official.
- [Community MCP](community.md) - 21 of 293 entries. A working server exists but somebody other than the vendor built it. It can be abandoned without the vendor noticing.
- [MCP unknown](unknown.md) - 7 of 293 entries. The check could not settle it either way. Unknown is a legal answer and it is published rather than guessed.
- [MCP not applicable](n-a.md) - 4 of 293 entries. An MCP server is not a meaningful question for this entry.
- [No MCP found](none-found.md) - 117 of 293 entries. No server was found at the time of the check. That is a statement about the search, not a promise that none exists.