topic-scorer.pixelcove.co/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-021 | OK | — | 307 | 5 | 719a4979a603ea07… | |
| REL-SNAP-022 | OK | — | 342 | 5 | 719a4979a603ea07… | |
| REL-SNAP-023 | OK | — | 506 | 5 | 719a4979a603ea07… | |
| REL-SNAP-024 | OK | — | 289 | 5 | 719a4979a603ea07… | |
| REL-SNAP-025 | OK | — | 291 | 5 | 719a4979a603ea07… | |
| REL-SNAP-026 | OK | — | 287 | 5 | 719a4979a603ea07… |
Identity
- Record key
topic-scorer.pixelcove.co/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- co.pixelcove/topic-scorer 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
- topic-scorer 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.