agents.releases.sh/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-039 | OK | — | 1017 | 16 | da5f95d8b78bc0f2… | |
| REL-SNAP-040 | OK | — | 828 | 16 | da5f95d8b78bc0f2… | |
| REL-SNAP-041 | OK | — | 783 | 16 | da5f95d8b78bc0f2… | |
| REL-SNAP-042 | OK | — | 624 | 16 | da5f95d8b78bc0f2… | |
| REL-SNAP-043 | OK | — | 163 | 16 | da5f95d8b78bc0f2… | |
| REL-SNAP-044 | OK | — | 682 | 16 | da5f95d8b78bc0f2… | |
| REL-SNAP-045 | OK | — | 870 | 16 | da5f95d8b78bc0f2… | |
| REL-SNAP-046 | OK | — | 960 | 16 | da5f95d8b78bc0f2… | |
| REL-SNAP-047 | OK | — | 96 | 16 | da5f95d8b78bc0f2… | |
| REL-SNAP-048 | OK | — | 970 | 16 | da5f95d8b78bc0f2… | |
| REL-SNAP-049 | OK | — | 211 | 16 | da5f95d8b78bc0f2… | |
| REL-SNAP-050 | OK | — | 1281 | 18 | 0dfbe04cec577c69… | |
| REL-SNAP-051 | OK | — | 1231 | 18 | 0dfbe04cec577c69… | |
| REL-SNAP-052 | OK | — | 1073 | 18 | 0dfbe04cec577c69… | |
| REL-SNAP-053 | OK | — | 2690 | 18 | 0dfbe04cec577c69… | |
| REL-SNAP-054 | OK | — | 2628 | 18 | 0dfbe04cec577c69… | |
| REL-SNAP-055 | OK | — | 702 | 18 | 0dfbe04cec577c69… | |
| REL-SNAP-056 | OK | — | 207 | 18 | 0dfbe04cec577c69… | |
| REL-SNAP-057 | OK | — | 138 | 18 | 0dfbe04cec577c69… | |
| REL-SNAP-058 | OK | — | 659 | 18 | 0dfbe04cec577c69… | |
| REL-SNAP-059 | OK | — | 674 | 18 | 0dfbe04cec577c69… |
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
agents.releases.sh/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- sh.releases/mcp 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
- releases 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.