sssnack.com/api/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-008 | OK | — | 111 | 10 | d3ab15e9df504717… | |
| REL-SNAP-009 | OK | — | 109 | 10 | d3ab15e9df504717… | |
| REL-SNAP-010 | OK | — | 134 | 11 | 4dfd0850dcc0d72b… | |
| REL-SNAP-011 | OK | — | 205 | 11 | 4dfd0850dcc0d72b… | |
| REL-SNAP-012 | OK | — | 170 | 11 | 4dfd0850dcc0d72b… | |
| REL-SNAP-013 | OK | — | 314 | 11 | 4dfd0850dcc0d72b… | |
| REL-SNAP-014 | OK | — | 97 | 11 | 4dfd0850dcc0d72b… | |
| REL-SNAP-015 | OK | — | 461 | 11 | 4dfd0850dcc0d72b… | |
| REL-SNAP-016 | OK | — | 200 | 11 | 4dfd0850dcc0d72b… | |
| REL-SNAP-017 | OK | — | 189 | 11 | 4dfd0850dcc0d72b… | |
| REL-SNAP-018 | OK | — | 439 | 11 | 4dfd0850dcc0d72b… | |
| REL-SNAP-019 | OK | — | 353 | 11 | 2034392a0a1e9fb4… | |
| REL-SNAP-020 | OK | — | 373 | 11 | 2034392a0a1e9fb4… | |
| REL-SNAP-021 | OK | — | 385 | 11 | 2034392a0a1e9fb4… | |
| REL-SNAP-022 | OK | — | 584 | 13 | a28bc5c5232f9f4a… | |
| REL-SNAP-023 | OK | — | 359 | 13 | a28bc5c5232f9f4a… | |
| REL-SNAP-024 | OK | — | 556 | 13 | a28bc5c5232f9f4a… | |
| REL-SNAP-025 | OK | — | 468 | 13 | 0cf3afc476300f5a… | |
| REL-SNAP-026 | OK | — | 240 | 27 | 8699ea901bd40e89… |
Tool schema changed 5 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
sssnack.com/api/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.sssnack/sssnack 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
- com.sssnack/sssnack 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.