www.mentiondrop.com/api/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-006 | OK | — | 829 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-007 | OK | — | 714 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-008 | OK | — | 576 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-009 | OK | — | 594 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-010 | OK | — | 637 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-011 | OK | — | 866 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-012 | OK | — | 825 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-013 | OK | — | 738 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-014 | OK | — | 585 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-015 | OK | — | 332 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-016 | OK | — | 333 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-017 | OK | — | 377 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-018 | OK | — | 326 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-019 | OK | — | 307 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-020 | OK | — | 315 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-021 | OK | — | 390 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-022 | OK | — | 400 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-023 | OK | — | 410 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-024 | OK | — | 347 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-025 | OK | — | 328 | 11 | a1e574fd1be6b4e9… | |
| REL-SNAP-026 | OK | — | 317 | 11 | a1e574fd1be6b4e9… |
Identity
- Record key
www.mentiondrop.com/api/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.mentiondrop/mentiondrop 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
- mentiondrop 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.