gateway.pipeworx.io/data-denver/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-002OK2834469029c273b5bc60…
REL-SNAP-003OK2634469029c273b5bc60…
REL-SNAP-004OK3434469029c273b5bc60…
REL-SNAP-005OK2834469029c273b5bc60…
REL-SNAP-006OK3134469029c273b5bc60…
REL-SNAP-007OK3334469029c273b5bc60…
REL-SNAP-008OK4434107f3b9db369d0df…
REL-SNAP-009OK2934107f3b9db369d0df…
REL-SNAP-010OK3434107f3b9db369d0df…
REL-SNAP-011OK4234107f3b9db369d0df…
REL-SNAP-012OK5134107f3b9db369d0df…
REL-SNAP-013OK3234107f3b9db369d0df…
REL-SNAP-014OK4434107f3b9db369d0df…
REL-SNAP-015OK523480cc0126ffa3b11f…
REL-SNAP-016OK603480cc0126ffa3b11f…

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
gateway.pipeworx.io/data-denver/mcp — the normalised endpoint observed. See the methodology for the rule.
Transport
streamable-http
Registry names (not anchored)
io.github.pipeworx-io/data-denver 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
pipeworx-gateway 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