sandbox.weverpay.com/api/wever-pay/sandbox/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-015 | OK | — | 390 | 3 | be4356171343b987… | |
| REL-SNAP-016 | OK | — | 400 | 3 | be4356171343b987… | |
| REL-SNAP-017 | OK | — | 373 | 3 | be4356171343b987… | |
| REL-SNAP-018 | OK | — | 404 | 3 | be4356171343b987… | |
| REL-SNAP-019 | OK | — | 381 | 3 | be4356171343b987… | |
| REL-SNAP-020 | OK | — | 399 | 3 | be4356171343b987… | |
| REL-SNAP-021 | OK | — | 415 | 3 | be4356171343b987… |
Identity
- Record key
sandbox.weverpay.com/api/wever-pay/sandbox/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.weverpay/public-testnet-alpha 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
- wever-pay-public-sandbox 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.