mcp.messora.dev/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-008 | OK | — | 719 | 5 | 033f18df4f600b38… | |
| REL-SNAP-009 | OK | — | 756 | 5 | a207efde9a9618bc… | |
| REL-SNAP-010 | OK | — | 764 | 5 | a207efde9a9618bc… | |
| REL-SNAP-011 | OK | — | 747 | 5 | a207efde9a9618bc… | |
| REL-SNAP-012 | OK | — | 772 | 5 | a207efde9a9618bc… | |
| REL-SNAP-013 | OK | — | 746 | 5 | a207efde9a9618bc… | |
| REL-SNAP-014 | OK | — | 1551 | 5 | a207efde9a9618bc… | |
| REL-SNAP-015 | OK | — | 875 | 5 | a207efde9a9618bc… | |
| REL-SNAP-016 | OK | — | 418 | 5 | a207efde9a9618bc… | |
| REL-SNAP-017 | OK | — | 417 | 5 | a207efde9a9618bc… | |
| REL-SNAP-018 | OK | — | 419 | 5 | a207efde9a9618bc… | |
| REL-SNAP-019 | OK | — | 417 | 5 | a207efde9a9618bc… | |
| REL-SNAP-020 | OK | — | 3999 | 5 | a207efde9a9618bc… | |
| REL-SNAP-021 | OK | — | 414 | 5 | a207efde9a9618bc… | |
| REL-SNAP-022 | OK | — | 416 | 5 | a207efde9a9618bc… | |
| REL-SNAP-023 | OK | — | 820 | 5 | a207efde9a9618bc… | |
| REL-SNAP-024 | OK | — | 414 | 5 | a207efde9a9618bc… | |
| REL-SNAP-025 | OK | — | 422 | 5 | a207efde9a9618bc… | |
| REL-SNAP-026 | OK | — | 415 | 5 | a207efde9a9618bc… |
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.messora.dev/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- dev.messora/messora 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
- MESSORA 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.