mcp.knowmapped.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-023 | OK | — | 505 | 10 | f8ef758c5f0d2baa… | |
| REL-SNAP-024 | OK | — | 410 | 10 | f8ef758c5f0d2baa… | |
| REL-SNAP-025 | OK | — | 370 | 10 | f8ef758c5f0d2baa… | |
| REL-SNAP-026 | OK | — | 395 | 10 | f8ef758c5f0d2baa… |
Identity
- Record key
mcp.knowmapped.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.knowmapped/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
- KnowMapped 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.