api.assetfare.dev/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-042 | OK | — | 502 | 13 | 37ae23aa349985b1… | |
| REL-SNAP-043 | OK | — | 517 | 13 | 37ae23aa349985b1… | |
| REL-SNAP-044 | OK | — | 506 | 15 | b9b2efad20e1cc44… | |
| REL-SNAP-045 | OK | — | 504 | 15 | b9b2efad20e1cc44… | |
| REL-SNAP-046 | OK | — | 513 | 15 | b9b2efad20e1cc44… | |
| REL-SNAP-047 | OK | — | 1177 | 22 | 4cdbddfe72674ac9… | |
| REL-SNAP-048 | OK | — | 523 | 22 | 4cdbddfe72674ac9… | |
| REL-SNAP-049 | OK | — | 1028 | 22 | 4cdbddfe72674ac9… | |
| REL-SNAP-050 | OK | — | 508 | 22 | cefe368c91329e00… | |
| REL-SNAP-051 | OK | — | 518 | 9 | b6763d827e7704ff… | |
| REL-SNAP-052 | OK | — | 1012 | 9 | d476365f06dcbafa… | |
| REL-SNAP-053 | OK | — | 1629 | 9 | c8020a8528ca8ddb… | |
| REL-SNAP-054 | OK | — | 517 | 9 | f12b626e32d2ee42… | |
| REL-SNAP-055 | OK | — | 1003 | 9 | f12b626e32d2ee42… | |
| REL-SNAP-056 | OK | — | 522 | 9 | d9a081e076abd684… | |
| REL-SNAP-057 | OK | — | 520 | 9 | d9a081e076abd684… | |
| REL-SNAP-058 | OK | — | 986 | 9 | cc1307dc201285ca… | |
| REL-SNAP-059 | OK | — | 471 | 9 | cc1307dc201285ca… |
Tool schema changed 9 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— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.odaiin/assetfare, io.github.assetfare/assetfare 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.