asha.news/api/v1/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-016OK6821994f2e66cb2b83fb…
REL-SNAP-017OK7721994f2e66cb2b83fb…
REL-SNAP-018OK9921994f2e66cb2b83fb…
REL-SNAP-019OK6921994f2e66cb2b83fb…
REL-SNAP-020OK11821994f2e66cb2b83fb…
REL-SNAP-021OK6821994f2e66cb2b83fb…
REL-SNAP-022OK8021994f2e66cb2b83fb…
REL-SNAP-023OK7321994f2e66cb2b83fb…
REL-SNAP-024OK6825fc367cbb3138ab24…
REL-SNAP-025OK7725fc367cbb3138ab24…
REL-SNAP-026OK7725fc367cbb3138ab24…

Tool schema changed 1 time 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
asha.news/api/v1/mcp — the normalised endpoint observed. See the methodology for the rule.
Transport
streamable-http
Registry names (not anchored)
news.asha/asha-news 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
Asha News 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