api.assetfare.dev/mcp/bridge

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-050OK—163522cefe368c91329e00…
REL-SNAP-051OK—10079b6763d827e7704ff…
REL-SNAP-052OK—5049d476365f06dcbafa…
REL-SNAP-053OK—5019c8020a8528ca8ddb…
REL-SNAP-054OK—5099f12b626e32d2ee42…
REL-SNAP-055OK—5139f12b626e32d2ee42…
REL-SNAP-056OK—5269d9a081e076abd684…
REL-SNAP-057OK—5219d9a081e076abd684…
REL-SNAP-058OK—4989cc1307dc201285ca…
REL-SNAP-059OK—4739cc1307dc201285ca…

Tool schema changed 6 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
api.assetfare.dev/mcp/bridge — the normalised endpoint observed. See the methodology for the rule.
Transport
streamable-http
Registry names (not anchored)
io.github.odaiin/assetfare-bridge, io.github.assetfare/assetfare-bridge 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. — more than one registry name refers to this single endpoint. We record both rather than choosing between them; the observation covers the endpoint and cannot be attributed to one of them.
Name reported by the server
AssetFare 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