# PulseMCP: MCP server status, API access gate and what it does > A community-run browsable directory and news hub for the MCP ecosystem (servers, clients, use cases, and a... MCP not applicable, Free to start. 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) / PulseMCP # PulseMCP [MCP not applicable](../mcp/n-a.md) [Free to start](../gates/free.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: [pulsemcp.com](https://pulsemcp.com) · entry id 07-pulsemcp · source 07-mcp-infrastructure.md line 136 **What it does** A community-run browsable directory and news hub for the MCP ecosystem (servers, clients, use cases, and a newsletter called "The Agentic Loop") that links out to third-party servers rather than hosting them. **AI features, separated from automation with an AI label on it** none - an information/discovery site. **RevOps role** A discovery/news layer for staying current on the MCP ecosystem rather than a connector a RevOps stack integrates with directly. **MCP server** - **Status bucket**: MCP not applicable - **Auth**: n/a - it is a directory; auth happens with whichever server you follow a link to, not with PulseMCP itself. - **Parsed URLs**: 1 found in the mcp_url field An MCP server is not a meaningful question for this entry. The status was established on 2026-08-24 and has not been re-fetched since. mcp_status, verbatim from the file: n/a (PulseMCP is a directory, not a vendor MCP) mcp_url, verbatim from the file: https://www.pulsemcp.com - [https://www.pulsemcp.com](https://www.pulsemcp.com) **Access gate** - **Gate bucket**: Free to start - **Can a solo operator reach it**: Yes, without talking to anyone api_gate, verbatim from the file: free (no pricing found; positioned as a free community resource) **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** - [Discover MCP servers](../jobs/discover-mcp-servers.md) A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records. Tagged by machine-pass on 2026-08-25 against the closed 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total. **Sources** - [https://www.pulsemcp.com](https://www.pulsemcp.com) 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://www.pulsemcp.com **Notes, verbatim from the file** As of this check, PulseMCP stated new server submissions and listing changes were paused "until mid-August" while it reworked its ingestion process - worth rechecking freshness before citing its listings as current. Maintained in part by a member of the MCP Steering Committee, giving it some standing as an unofficial-but-credible hub alongside the official GitHub registry. **Provenance** - **Entry id**: 07-pulsemcp - **Source file**: 07-mcp-infrastructure.md - **Source line**: 136 - **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).