agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-040 | OK | — | 539 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-041 | OK | — | 735 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-042 | OK | — | 545 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-043 | OK | — | 558 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-044 | OK | — | 551 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-045 | OK | — | 567 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-046 | OK | — | 557 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-047 | OK | — | 552 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-048 | OK | — | 817 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-049 | OK | — | 543 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-050 | OK | — | 540 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-051 | OK | — | 798 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-052 | OK | — | 551 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-053 | OK | — | 547 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-054 | OK | — | 550 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-055 | OK | — | 551 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-056 | OK | — | 552 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-057 | OK | — | 553 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-058 | OK | — | 558 | 1 | 3c6eec1ea5e67de6… | |
| REL-SNAP-059 | OK | — | 561 | 1 | 3c6eec1ea5e67de6… |
Identity
- Record key
agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.TAMA-FIT/agent-commerce-readiness 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
- agent-commerce-readiness 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.