gateway.pipeworx.io/chaos-index/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-002OK2732c543708d15ee2873…
REL-SNAP-003OK2932c543708d15ee2873…
REL-SNAP-004OK3032c543708d15ee2873…
REL-SNAP-005OK3732c543708d15ee2873…
REL-SNAP-006OK3632c543708d15ee2873…
REL-SNAP-007OK3332c543708d15ee2873…
REL-SNAP-008OK5332f276b4ea8f61b927…
REL-SNAP-009OK3632f276b4ea8f61b927…
REL-SNAP-010OK3632f276b4ea8f61b927…
REL-SNAP-011OK3632f276b4ea8f61b927…
REL-SNAP-012OK3732f276b4ea8f61b927…
REL-SNAP-013OK3032f276b4ea8f61b927…
REL-SNAP-014OK8032f276b4ea8f61b927…
REL-SNAP-015OK563220ed71f9ef0e7202…
REL-SNAP-016OK543220ed71f9ef0e7202…

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