submitmap.com/api/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-009 | OK | — | 45 | 11 | fa1fbd25655011b0… | |
| REL-SNAP-010 | OK | — | 47 | 11 | 0e2f183192004b71… | |
| REL-SNAP-011 | OK | — | 46 | 11 | 0e2f183192004b71… | |
| REL-SNAP-012 | OK | — | 94 | 11 | 7dd1e1b7d596add7… | |
| REL-SNAP-013 | OK | — | 51 | 11 | 7dd1e1b7d596add7… | |
| REL-SNAP-014 | OK | — | 166 | 11 | 7dd1e1b7d596add7… | |
| REL-SNAP-015 | OK | — | 57 | 11 | 7dd1e1b7d596add7… | |
| REL-SNAP-016 | OK | — | 70 | 11 | da11ae94b78bc9ea… | |
| REL-SNAP-017 | OK | — | 85 | 11 | ab69e3bb5cad949c… | |
| REL-SNAP-018 | OK | — | 60 | 11 | ab69e3bb5cad949c… | |
| REL-SNAP-019 | OK | — | 66 | 11 | 6d2a8217b25f2e55… | |
| REL-SNAP-020 | OK | — | 57 | 11 | 6d2a8217b25f2e55… | |
| REL-SNAP-021 | OK | — | 61 | 11 | 734b47fea1bd8a8c… | |
| REL-SNAP-022 | OK | — | 82 | 11 | 734b47fea1bd8a8c… | |
| REL-SNAP-023 | OK | — | 56 | 11 | 734b47fea1bd8a8c… | |
| REL-SNAP-024 | OK | — | 69 | 11 | 591d96d937237537… | |
| REL-SNAP-025 | OK | — | 79 | 11 | 13890b7f4c99e232… | |
| REL-SNAP-026 | OK | — | 70 | 11 | 13890b7f4c99e232… |
Tool schema changed 8 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
submitmap.com/api/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.submitmap/directory 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
- submitmap 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.