cryptodata-api.datachain.workers.dev/mcp

Last observed:— recorded as OK

Observations

Every observation recorded for this endpoint, oldest first. Each row is a separate look, not a summary.
ObservedSnapshotRecorded asDetailLatency (ms)ToolsTool schema fingerprint
REL-SNAP-002OK773484a7940f593185114…
REL-SNAP-003OK884484a7940f593185114…
REL-SNAP-004OK1066484a7940f593185114…
REL-SNAP-005OK771484a7940f593185114…
REL-SNAP-006OK778484a7940f593185114…
REL-SNAP-007OK820484a7940f593185114…
REL-SNAP-008OK808484a7940f593185114…
REL-SNAP-009OK791484a7940f593185114…
REL-SNAP-010OK786484a7940f593185114…
REL-SNAP-011OK783484a7940f593185114…
REL-SNAP-012OK813484a7940f593185114…
REL-SNAP-013OK995484a7940f593185114…
REL-SNAP-014OK828484a7940f593185114…
REL-SNAP-015OK162484a7940f593185114…
REL-SNAP-016OK60484a7940f593185114…

Identity

Record key
cryptodata-api.datachain.workers.dev/mcp — the normalised endpoint observed. See the methodology for the rule.
Transport
streamable-http
Registry names (not anchored)
io.github.elevasyncsolutions-jpg/cryptodata-api 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
CryptoData API 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.

Plain-text version of this page