bounty.brelsfordsoftware.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-024 | OK | — | 126 | 11 | 9b4ef764cb40fd99… | |
| REL-SNAP-025 | OK | — | 313 | 11 | 9b4ef764cb40fd99… | |
| REL-SNAP-026 | OK | — | 116 | 14 | 2e421aa8e527df34… |
Tool schema changed 1 time 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
bounty.brelsfordsoftware.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.brelsfordsoftware/agent-bounty-jobs 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
- agent-bounty-jobs 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.