mcp.proship.me/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-014OK7411a922e5220ae32745…
REL-SNAP-015OK45811a922e5220ae32745…
REL-SNAP-016OK42611a922e5220ae32745…
REL-SNAP-017OK56311a922e5220ae32745…
REL-SNAP-018OK46811a922e5220ae32745…
REL-SNAP-019OK60811a922e5220ae32745…
REL-SNAP-020OK38011a922e5220ae32745…
REL-SNAP-021OK50811a922e5220ae32745…
REL-SNAP-022OK51811a922e5220ae32745…
REL-SNAP-023OK45111a922e5220ae32745…
REL-SNAP-024OK34911a922e5220ae32745…
REL-SNAP-025OK64711a922e5220ae32745…
REL-SNAP-026OK34311a922e5220ae32745…

Identity

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