api.hungry-esim.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-013 | OK | — | 710 | 8 | 0acad32d355f13f1… | |
| REL-SNAP-014 | OK | — | 672 | 10 | 212f05b39d24c15b… | |
| REL-SNAP-015 | OK | — | 804 | 10 | 212f05b39d24c15b… | |
| REL-SNAP-016 | OK | — | 375 | 10 | 212f05b39d24c15b… |
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
api.hungry-esim.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.hungry-esim/esim 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
- hungry-esim 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.