api.hyperping.io/v1/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 454 | 26 | 2df78b2fdabbe9b0… | |
| REL-SNAP-003 | OK | — | 399 | 26 | 2df78b2fdabbe9b0… | |
| REL-SNAP-004 | OK | — | 393 | 26 | 2df78b2fdabbe9b0… | |
| REL-SNAP-005 | OK | — | 400 | 26 | 2df78b2fdabbe9b0… | |
| REL-SNAP-006 | OK | — | 485 | 26 | 2df78b2fdabbe9b0… | |
| REL-SNAP-007 | OK | — | 436 | 26 | 2df78b2fdabbe9b0… | |
| REL-SNAP-008 | OK | — | 491 | 26 | 2df78b2fdabbe9b0… | |
| REL-SNAP-009 | OK | — | 414 | 26 | 2df78b2fdabbe9b0… | |
| REL-SNAP-010 | OK | — | 424 | 26 | 2df78b2fdabbe9b0… | |
| REL-SNAP-011 | OK | — | 4546 | 26 | 2df78b2fdabbe9b0… | |
| REL-SNAP-012 | OK | — | 413 | 26 | 2df78b2fdabbe9b0… | |
| REL-SNAP-013 | OK | — | 408 | 26 | 2df78b2fdabbe9b0… | |
| REL-SNAP-014 | OK | — | 549 | 26 | 2df78b2fdabbe9b0… | |
| REL-SNAP-015 | OK | — | 100 | 26 | 2df78b2fdabbe9b0… | |
| REL-SNAP-016 | OK | — | 113 | 26 | 2df78b2fdabbe9b0… |
Identity
- Record key
api.hyperping.io/v1/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.hyperping/hyperping 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
- hyperping-monitors 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.