> NOTICE — Pre-launch build. Every record here is a dated observation of a real MCP endpoint operated by a third party, rendered from the published archive. Coverage is partial — the figures cover the snapshots in the export this build was made from, not the whole chain and not the whole ecosystem. Claims and badges are not open.

# agentresolver.vercel.app/mcp/control

Last observed: 2026-09-21T09:39:18.762Z
Recorded as: OK
Transport: streamable-http
Observations held: 3
Published: yes

## Observations

| Observed | Snapshot | Recorded as | Detail | Latency ms | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| 2026-09-19T09:41:30.296Z | REL-SNAP-046 | OK | - | 351 | 2 | 274c2575bb77069712058306e9b7a8d3a81108e1ffd0b8e4b8121618cc201a6f |
| 2026-09-20T09:58:22.078Z | REL-SNAP-047 | OK | - | 298 | 2 | 274c2575bb77069712058306e9b7a8d3a81108e1ffd0b8e4b8121618cc201a6f |
| 2026-09-21T09:39:18.762Z | REL-SNAP-048 | OK | - | 275 | 2 | 274c2575bb77069712058306e9b7a8d3a81108e1ffd0b8e4b8121618cc201a6f |

## Identity

Record key: agentresolver.vercel.app/mcp/control (the normalised endpoint observed)
Registry names (not anchored — no inclusion proof reaches this field): io.github.waxsway/agentresolver (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)
Name reported by the server: agentresolver-control (self-reported, unverified, never used as identity)

Each observation carries a merkle leaf in the snapshot it belongs to. The chain
establishes that a root existed by a given time; it does not establish that any
measurement is true.