mcp.shumi.ai/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-009 | OK | — | 409 | 31 | e51534a1c9d3a4cc… | |
| REL-SNAP-010 | OK | — | 615 | 31 | e51534a1c9d3a4cc… | |
| REL-SNAP-011 | OK | — | 399 | 31 | e51534a1c9d3a4cc… | |
| REL-SNAP-012 | OK | — | 545 | 31 | e51534a1c9d3a4cc… | |
| REL-SNAP-013 | OK | — | 417 | 31 | e51534a1c9d3a4cc… | |
| REL-SNAP-014 | OK | — | 567 | 31 | e51534a1c9d3a4cc… | |
| REL-SNAP-015 | OK | — | 142 | 31 | e51534a1c9d3a4cc… | |
| REL-SNAP-016 | OK | — | 152 | 31 | 956ebc22dfdfb0cd… | |
| REL-SNAP-017 | OK | — | 153 | 31 | 956ebc22dfdfb0cd… | |
| REL-SNAP-018 | OK | — | 166 | 31 | 956ebc22dfdfb0cd… | |
| REL-SNAP-019 | OK | — | 131 | 31 | 956ebc22dfdfb0cd… | |
| REL-SNAP-020 | OK | — | 171 | 31 | 956ebc22dfdfb0cd… | |
| REL-SNAP-021 | OK | — | 154 | 31 | 956ebc22dfdfb0cd… | |
| REL-SNAP-022 | OK | — | 129 | 31 | 956ebc22dfdfb0cd… | |
| REL-SNAP-023 | OK | — | 157 | 31 | 956ebc22dfdfb0cd… | |
| REL-SNAP-024 | OK | — | 144 | 31 | 956ebc22dfdfb0cd… | |
| REL-SNAP-025 | OK | — | 162 | 31 | 956ebc22dfdfb0cd… | |
| REL-SNAP-026 | OK | — | 178 | 31 | 956ebc22dfdfb0cd… |
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.shumi.ai/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- ai.shumi/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
- shumi 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.