caper.network/api/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-009 | OK | — | 526 | 8 | a9af3abba64de433… | |
| REL-SNAP-010 | OK | — | 1666 | 13 | 7892d25d486d462a… | |
| REL-SNAP-011 | OK | — | 594 | 13 | 7892d25d486d462a… | |
| REL-SNAP-012 | OK | — | 635 | 13 | df956cb14480ed4b… | |
| REL-SNAP-013 | OK | — | 615 | 13 | df956cb14480ed4b… | |
| REL-SNAP-014 | OK | — | 652 | 13 | df956cb14480ed4b… | |
| REL-SNAP-015 | OK | — | 350 | 13 | df956cb14480ed4b… | |
| REL-SNAP-016 | OK | — | 315 | 13 | df956cb14480ed4b… | |
| REL-SNAP-017 | OK | — | 304 | 13 | df956cb14480ed4b… | |
| REL-SNAP-018 | OK | — | 313 | 13 | df956cb14480ed4b… | |
| REL-SNAP-019 | OK | — | 375 | 13 | df956cb14480ed4b… | |
| REL-SNAP-020 | OK | — | 439 | 13 | df956cb14480ed4b… | |
| REL-SNAP-021 | OK | — | 291 | 13 | df956cb14480ed4b… | |
| REL-SNAP-022 | OK | — | 353 | 13 | df956cb14480ed4b… | |
| REL-SNAP-023 | OK | — | 490 | 13 | df956cb14480ed4b… | |
| REL-SNAP-024 | OK | — | 339 | 13 | bc504401d979ebba… | |
| REL-SNAP-025 | OK | — | 342 | 13 | bc504401d979ebba… | |
| REL-SNAP-026 | OK | — | 337 | 13 | db0a7456c2327a12… |
Tool schema changed 4 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
caper.network/api/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- network.caper/caper-wiki 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
- caper-wiki 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.