scenef.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-008 | OK | — | 638 | 9 | e03619be955fcff2… | |
| REL-SNAP-009 | OK | — | 687 | 9 | e03619be955fcff2… | |
| REL-SNAP-010 | OK | — | 651 | 9 | e03619be955fcff2… | |
| REL-SNAP-011 | OK | — | 729 | 9 | e03619be955fcff2… | |
| REL-SNAP-012 | OK | — | 946 | 9 | e03619be955fcff2… | |
| REL-SNAP-013 | OK | — | 630 | 9 | e03619be955fcff2… | |
| REL-SNAP-014 | OK | — | 637 | 9 | e03619be955fcff2… | |
| REL-SNAP-015 | OK | — | 450 | 9 | e03619be955fcff2… | |
| REL-SNAP-016 | OK | — | 576 | 9 | e03619be955fcff2… | |
| REL-SNAP-017 | OK | — | 352 | 9 | e03619be955fcff2… | |
| REL-SNAP-018 | OK | — | 425 | 9 | e03619be955fcff2… | |
| REL-SNAP-019 | OK | — | 595 | 9 | e03619be955fcff2… | |
| REL-SNAP-020 | OK | — | 378 | 9 | e03619be955fcff2… | |
| REL-SNAP-021 | OK | — | 558 | 9 | e03619be955fcff2… | |
| REL-SNAP-022 | OK | — | 382 | 9 | e03619be955fcff2… | |
| REL-SNAP-023 | OK | — | 367 | 9 | 426980a6284e9568… | |
| REL-SNAP-024 | OK | — | 481 | 9 | b6acd9af73dc3280… | |
| REL-SNAP-025 | OK | — | 366 | 9 | b6acd9af73dc3280… | |
| REL-SNAP-026 | OK | — | 519 | 9 | b6acd9af73dc3280… |
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
scenef.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.scenef/showtimes 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
- scenef 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.