freight.dropwatchhq.com/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-002OK5296074d41270041881…
REL-SNAP-003OK5696074d41270041881…
REL-SNAP-004OK6596074d41270041881…
REL-SNAP-005OK7496074d41270041881…
REL-SNAP-006OK6396074d41270041881…
REL-SNAP-007OK6396074d41270041881…
REL-SNAP-008OK8096074d41270041881…
REL-SNAP-009OK6796074d41270041881…
REL-SNAP-010OK13596074d41270041881…
REL-SNAP-011OK8296074d41270041881…
REL-SNAP-012OK11296074d41270041881…
REL-SNAP-013OK6896074d41270041881…
REL-SNAP-014OK19296074d41270041881…
REL-SNAP-015OK11596074d41270041881…
REL-SNAP-016OK12296074d41270041881…

Identity

Record key
freight.dropwatchhq.com/mcp — the normalised endpoint observed. See the methodology for the rule.
Transport
streamable-http
Registry names (not anchored)
com.dropwatchhq/freight-intel 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
freight-intel 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