api.signalbureau.ai/api/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-013 | OK | — | 741 | 21 | 725b99ff0e354ab9… | |
| REL-SNAP-014 | OK | — | 1040 | 21 | 70713081f1ba3025… | |
| REL-SNAP-015 | OK | — | 380 | 21 | e0837ead5784807d… | |
| REL-SNAP-016 | OK | — | 402 | 21 | 9d4fbf99e1576eff… |
Tool schema changed 3 times across this history — the fingerprint differs between consecutive observations. A change can occur while the tool count stays identical, which is why the fingerprint is recorded alongside the count.
Identity
- Record key
api.signalbureau.ai/api/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.evolutionlabs-dev/signal-bureau What the registry said when we swept it, as observed by us — not evidence that the registry was correct, that the name belongs to whoever registered it, or that it still resolves. Not covered by the chain: no inclusion proof reaches this field.
- Name reported by the server
- signal-bureau Self-reported and unverified — never used as identity.
Verifying this record
Each observation above carries a merkle leaf in the published snapshot it belongs to. Verify the chain explains how to walk a leaf to a published root without taking our word for any of it.