Bounded software search, unknown requirements, and the origins of project identifiers.
Connect Remote server
claude mcp add --transport http provenance https://www.pulsegate.ai/api/mcp
{
"mcpServers": {
"provenance": {
"url": "https://www.pulsegate.ai/api/mcp"
}
}
}
{
"servers": {
"provenance": {
"type": "http",
"url": "https://www.pulsegate.ai/api/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://www.pulsegate.ai/api/mcp
Tools 3 found in our last check
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, publisher fetch, bulk export or functionalit…
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, or by an identifier you already have.
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.
Details
| Endpoint | https://www.pulsegate.ai/api/mcp (Streamable HTTP) |
| First published | 13 Oct 2026 |
| Last updated | 13 Oct 2026 |
| Registry name | ai.pulsegate/provenance |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
