# Pulsegate Provenance MCP server

Source: https://glimind.com/server/mcp-registry%2Fai.pulsegate%2Fprovenance
Registry id: `mcp-registry/ai.pulsegate/provenance`
Status: live (checked 2026-10-27T16:04:32.014Z)

## Verdict

Pulsegate Provenance MCP server answered 98.53% of Glimind's liveness checks over 30 days, better than 6% of MCP servers, with 642 ms median handshake and 23 outages in 90 days. Its agent-readiness grade is A (93/100) across 3 tools, costing an agent about 672 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 98.53% | 6% of MCP servers |
| Median handshake latency | 642 ms | 32% of MCP servers |
| p95 handshake latency | 3037 ms | — |
| Checks in 30 days | 3,889 | — |
| Outages, 90 days | 23 | — |
| Median recovery | 8 min | — |
| Agent-readiness score | 93/100 (A) | 75% of MCP servers |
| Tools | 3 | — |
| Tool-list size for an agent | ~672 tokens | 83% of MCP servers |
| Days observed | 24 | — |

## Install

```json
{
  "mcpServers": {
    "pulsegate-provenance-mcp-server": {
      "type": "http",
      "url": "https://www.pulsegate.ai/api/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http pulsegate-provenance-mcp-server https://www.pulsegate.ai/api/mcp
```

## Tools (3)

- `list_identifier_platforms`: List every platform PulseGate records identifiers on, with how many identifiers it holds for each. Use it to learn the vocabulary the platform argument of looku
- `lookup_project`: Return 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 
- `search_catalog`: Find 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/u

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.