gateway.pipeworx.io/data-baltimore/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-002OK273412ba8f94ec4006a1…
REL-SNAP-003OK263412ba8f94ec4006a1…
REL-SNAP-004OK743412ba8f94ec4006a1…
REL-SNAP-005OK293412ba8f94ec4006a1…
REL-SNAP-006OK343412ba8f94ec4006a1…
REL-SNAP-007OK293412ba8f94ec4006a1…
REL-SNAP-008OK343437613e0979bdbefa…
REL-SNAP-009OK323437613e0979bdbefa…
REL-SNAP-010OK343437613e0979bdbefa…
REL-SNAP-011OK393437613e0979bdbefa…
REL-SNAP-012OK333437613e0979bdbefa…
REL-SNAP-013OK373437613e0979bdbefa…
REL-SNAP-014OK313437613e0979bdbefa…
REL-SNAP-015OK49341a81f63540840f01…
REL-SNAP-016OK55341a81f63540840f01…

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