404.directory/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-013OK—545621bcd50128f8122c6…
REL-SNAP-014OK—555621bcd50128f8122c6…
REL-SNAP-015OK—25121bcd50128f8122c6…
REL-SNAP-016OK—27621bcd50128f8122c6…
REL-SNAP-017OK—88521bcd50128f8122c6…
REL-SNAP-018OK—917——
REL-SNAP-019OK—1619——
REL-SNAP-020OK—1022——
REL-SNAP-021OK—1217——
REL-SNAP-022OK—1172——
REL-SNAP-023OK—1150——
REL-SNAP-024OK—1369——
REL-SNAP-025OK—903——
REL-SNAP-026OK—736——
REL-SNAP-027OK—1295——
REL-SNAP-028OK—645——
REL-SNAP-029OK—976——
REL-SNAP-030OK—875——
REL-SNAP-031OK—884——
REL-SNAP-032OK—2023——
REL-SNAP-033OK—1223——
REL-SNAP-034OK—1183——
REL-SNAP-035OK—1076——
REL-SNAP-036OK—967——
REL-SNAP-037OK—810——
REL-SNAP-038OK—1001——
REL-SNAP-039OK—2019——
REL-SNAP-040OK—798——
REL-SNAP-041OK—646——
REL-SNAP-042OK—1956——
REL-SNAP-043OK—1256——
REL-SNAP-044OK—1347——
REL-SNAP-045OK—682——
REL-SNAP-046HTTP_5XXhttp_500———
REL-SNAP-047HTTP_5XXhttp_500———
REL-SNAP-048HTTP_5XXhttp_500———
REL-SNAP-049HTTP_5XXhttp_500———
REL-SNAP-050HTTP_5XXhttp_500———
REL-SNAP-051HTTP_5XXhttp_500———
REL-SNAP-052HTTP_5XXhttp_500———
REL-SNAP-053HTTP_5XXhttp_500———
REL-SNAP-054HTTP_5XXhttp_503———
REL-SNAP-055HTTP_5XXhttp_500———
REL-SNAP-056HTTP_5XXhttp_500———
REL-SNAP-057PROTOCOL_ERRORpost_rejected———
REL-SNAP-058OK—632——
REL-SNAP-059OK—1149——

Identity

Record key
404.directory/mcp — the normalised endpoint observed. See the methodology for the rule.
Transport
streamable-http
Registry names (not anchored)
io.github.MM-sheng/404-directory 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
404.directory 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