narcoscope.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-009 | OK | — | 560 | 5 | ea28dfcf2c32bb6b… | |
| REL-SNAP-010 | OK | — | 639 | 5 | ea28dfcf2c32bb6b… | |
| REL-SNAP-011 | OK | — | 560 | 5 | ea28dfcf2c32bb6b… | |
| REL-SNAP-012 | OK | — | 866 | 5 | ea28dfcf2c32bb6b… | |
| REL-SNAP-013 | OK | — | 581 | 5 | ea28dfcf2c32bb6b… | |
| REL-SNAP-014 | OK | — | 844 | 5 | ea28dfcf2c32bb6b… | |
| REL-SNAP-015 | OK | — | 321 | 5 | ea28dfcf2c32bb6b… | |
| REL-SNAP-016 | OK | — | 343 | 5 | ea28dfcf2c32bb6b… | |
| REL-SNAP-017 | OK | — | 287 | 5 | ea28dfcf2c32bb6b… | |
| REL-SNAP-018 | OK | — | 345 | 5 | ea28dfcf2c32bb6b… | |
| REL-SNAP-019 | OK | — | 270 | 5 | ea28dfcf2c32bb6b… | |
| REL-SNAP-020 | OK | — | 269 | 5 | ea28dfcf2c32bb6b… | |
| REL-SNAP-021 | OK | — | 286 | 5 | ea28dfcf2c32bb6b… | |
| REL-SNAP-022 | OK | — | 274 | 5 | ea28dfcf2c32bb6b… | |
| REL-SNAP-023 | OK | — | 313 | 6 | 36ab23b50fd8f358… | |
| REL-SNAP-024 | OK | — | 299 | 6 | 36ab23b50fd8f358… | |
| REL-SNAP-025 | OK | — | 267 | 7 | 1d88509b556b2707… | |
| REL-SNAP-026 | OK | — | 297 | 7 | 1d88509b556b2707… |
Tool schema changed 2 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
narcoscope.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.beepboop2025/narcoscope 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
- narcoscope 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.