filingdesk.com/api/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-009 | OK | — | 607 | 8 | 3799664b2fcd44bc… | |
| REL-SNAP-010 | OK | — | 602 | 8 | 3799664b2fcd44bc… | |
| REL-SNAP-011 | OK | — | 590 | 8 | 3799664b2fcd44bc… | |
| REL-SNAP-012 | OK | — | 720 | 8 | 3799664b2fcd44bc… | |
| REL-SNAP-013 | OK | — | 603 | 8 | 3799664b2fcd44bc… | |
| REL-SNAP-014 | OK | — | 658 | 8 | 3799664b2fcd44bc… | |
| REL-SNAP-015 | OK | — | 340 | 8 | 3799664b2fcd44bc… | |
| REL-SNAP-016 | OK | — | 342 | 8 | 3799664b2fcd44bc… |
Identity
- Record key
filingdesk.com/api/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.filingdesk/data 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
- filingdesk-data 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.