# mcp.so: MCP server status, API access gate and what it does > A community MCP server/client directory (per its public reputation as one of the earlier MCP catalog sites) ... MCP unknown, Gate unknown. Checked 2026-08-24. *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) / [MCP Layer](../categories/mcp-infrastructure.md) / mcp.so # mcp.so [MCP unknown](../mcp/unknown.md) [Gate unknown](../gates/unknown.md) [MCP Layer](../categories/mcp-infrastructure.md) RESEARCHED Checked 2026-08-24 > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 0. Vendor: [mcp.so](https://mcp.so) · entry id 07-mcp-so · source 07-mcp-infrastructure.md line 156 **What it does** A community MCP server/client directory (per its public reputation as one of the earlier MCP catalog sites) - could not independently re-verify current content in this research pass. **AI features, separated from automation with an AI label on it** unknown **RevOps role** unknown - cannot confirm GTM-relevant server coverage without a successful fetch. **MCP server** - **Status bucket**: MCP unknown - **Auth**: unknown - **Parsed URLs**: 0 found in the mcp_url field The check could not settle it either way. Unknown is a legal answer and it is published rather than guessed. The status was established on 2026-08-24 and has not been re-fetched since. mcp_status, verbatim from the file: unknown mcp_url, verbatim from the file: none-found **Access gate** - **Gate bucket**: Gate unknown - **Can a solo operator reach it**: Not established api_gate, verbatim from the file: unknown 83 of 293 entries carry an unknown gate. Unknown is a legal answer and it ships as unknown rather than as a guess. **API documentation** No documentation URL recorded. 263 of 293 entries are in the same position. Blank is legal and it is published as blank. **GitHub health** Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build. The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale. **Jobs it can do** No job tag on this entry. Reason recorded by the tagging pass: unclear. The entry could not verify current content. discover-mcp-servers is the obvious tag and there is no fetched evidence for it. 22 of 293 entries are untagged. An empty list here means nobody has tagged this, not that the tool does nothing. The vocabulary is closed, so a tool whose job is genuinely not in it stays blank rather than being forced into the nearest tag. **Sources** - [https://mcp.so](https://mcp.so) - (attempted; site returned HTTP 403 to automated fetch on every attempt, including /servers) 1 source URL. Thin. The standing rule is at least two independent sources with the vendor's own site unable to be both of them, and this entry does not meet it. 32 entries are in the same state and they are listed on the methodology page. Raw sources field, verbatim: https://mcp.so (attempted; site returned HTTP 403 to automated fetch on every attempt, including /servers) **Notes, verbatim from the file** Per the two-tier honesty rule and the "no invented facts" law, this entry is intentionally thin - mcp.so blocked automated access (403 Forbidden) on every fetch attempt during this research pass, and web search was unavailable (session quota exhausted). Do not treat this listing as verified; re-run research with a live browser session before publishing anything more specific than "a community MCP directory exists at this URL." **Provenance** - **Entry id**: 07-mcp-so - **Source file**: 07-mcp-infrastructure.md - **Source line**: 156 - **Tier**: RESEARCHED - **last_checked**: 2026-08-24 - **Data baked**: 2026-08-25 Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).