mcp.payperbyte.io/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 596 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-003 | OK | — | 566 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-004 | OK | — | 572 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-005 | OK | — | 599 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-006 | OK | — | 614 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-007 | OK | — | 601 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-008 | OK | — | 685 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-009 | OK | — | 1100 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-010 | OK | — | 574 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-011 | OK | — | 630 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-012 | OK | — | 626 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-013 | OK | — | 569 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-014 | OK | — | 650 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-015 | OK | — | 313 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-016 | OK | — | 535 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-017 | OK | — | 510 | 15 | 41a560fd5bc02bf4… | |
| REL-SNAP-018 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-019 | OK | — | 505 | 15 | 1ccab6cf522aae99… | |
| REL-SNAP-020 | OK | — | 539 | 15 | 1ccab6cf522aae99… | |
| REL-SNAP-021 | OK | — | 318 | 15 | 1ccab6cf522aae99… | |
| REL-SNAP-022 | OK | — | 537 | 15 | 4a697f186ada28c9… | |
| REL-SNAP-023 | OK | — | 546 | 15 | 4a697f186ada28c9… | |
| REL-SNAP-024 | OK | — | 327 | 15 | 4a697f186ada28c9… | |
| REL-SNAP-025 | OK | — | 506 | 15 | 4a697f186ada28c9… | |
| REL-SNAP-026 | OK | — | 505 | 15 | 4a697f186ada28c9… |
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
mcp.payperbyte.io/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.0rkz/byte-protocol 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
- byte-protocol 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.