api.slideforge.dev/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 371 | 7 | c09fd82aa0639dad… | |
| REL-SNAP-003 | OK | — | 363 | 7 | 9b2b2fb05ab0434b… | |
| REL-SNAP-004 | OK | — | 764 | 7 | 9b2b2fb05ab0434b… | |
| REL-SNAP-005 | OK | — | 754 | 7 | 4b1f969393be6cdb… | |
| REL-SNAP-006 | OK | — | 799 | 7 | 4b1f969393be6cdb… | |
| REL-SNAP-007 | OK | — | 1179 | 7 | 7f6bd72a5f240d89… | |
| REL-SNAP-008 | OK | — | 710 | 7 | 7f6bd72a5f240d89… | |
| REL-SNAP-009 | OK | — | 720 | 7 | 7f6bd72a5f240d89… | |
| REL-SNAP-010 | OK | — | 719 | 7 | 7f6bd72a5f240d89… | |
| REL-SNAP-011 | OK | — | 718 | 7 | 7f6bd72a5f240d89… | |
| REL-SNAP-012 | OK | — | 777 | 7 | 7f6bd72a5f240d89… | |
| REL-SNAP-013 | OK | — | 755 | 7 | 7f6bd72a5f240d89… | |
| REL-SNAP-014 | OK | — | 779 | 7 | 6c97c0e74df109d5… | |
| REL-SNAP-015 | OK | — | 75 | 7 | 6c97c0e74df109d5… | |
| REL-SNAP-016 | OK | — | 67 | 7 | 6c97c0e74df109d5… |
Tool schema changed 4 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
api.slideforge.dev/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- dev.slideforge/slideforge 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
- slideforge 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.