PulseGate MCP server
Which servers in the official MCP registry are PulseGate's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-13
- Registry nameai.pulsegate/provenanceverified in the MCP registry
The registry name sits under pulsegate.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-13
- Tools3
- Server calls itselfpulsegate-provenance
- Server version0.2.2
- Protocol version2025-06-18
On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 282 ms.
search_catalogFind software by name, task or recorded filters. Returns at most ten candidates from the same service as native HTML/HTTP search, with recordUrl and met/unmet/unknown requirement assessments. Unknown is not false. No complete profile…
lookup_projectReturn the external identifiers PulseGate holds for one project, and for each one how it arrived and whether anyone has checked that it belongs. Makes no claim about whether the software is alive, maintained, or working. Look up by slug…
list_identifier_platformsList every platform PulseGate records identifiers on, with how many identifiers it holds for each. Use it to learn the vocabulary the platform argument of lookup_project accepts.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"provenance": {
"type": "http",
"url": "https://www.pulsegate.ai/api/mcp"
}
}
}OpenAPI spec
8 paths, read 2026-10-13. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.