mcp.nevent.ai
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-021 | OK | — | 235 | 59 | 9988051c73c89a65… | |
| REL-SNAP-022 | OK | — | 164 | 59 | 9988051c73c89a65… | |
| REL-SNAP-023 | OK | — | 111 | 59 | 9988051c73c89a65… | |
| REL-SNAP-024 | OK | — | 224 | 59 | 9988051c73c89a65… | |
| REL-SNAP-025 | OK | — | 107 | 59 | 9988051c73c89a65… | |
| REL-SNAP-026 | OK | — | 275 | 59 | 9988051c73c89a65… |
Identity
- Record key
mcp.nevent.ai— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.nevent-dev/mcp-nevent 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
- nevent-mcp 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.