a2awire.com/mcp/benchmarks/launch-recurring-bill-reconcile-2026-09-17-c9c2481b/http
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-045 | OK | — | 242 | 23 | 868143217f47f012… | |
| REL-SNAP-046 | OK | — | 327 | 23 | 868143217f47f012… | |
| REL-SNAP-047 | OK | — | 246 | 23 | 868143217f47f012… | |
| REL-SNAP-048 | OK | — | 271 | 23 | 868143217f47f012… | |
| REL-SNAP-049 | OK | — | 241 | 23 | 868143217f47f012… | |
| REL-SNAP-050 | OK | — | 2010 | 23 | 6415091bcb09388a… | |
| REL-SNAP-051 | OK | — | 253 | 23 | 6415091bcb09388a… | |
| REL-SNAP-052 | OK | — | 243 | 23 | f80a80fc7c880708… | |
| REL-SNAP-053 | OK | — | 342 | 23 | f80a80fc7c880708… | |
| REL-SNAP-054 | OK | — | 246 | 23 | f80a80fc7c880708… | |
| REL-SNAP-055 | OK | — | 243 | 23 | f80a80fc7c880708… | |
| REL-SNAP-056 | OK | — | 342 | 23 | f80a80fc7c880708… | |
| REL-SNAP-057 | OK | — | 251 | 23 | f80a80fc7c880708… | |
| REL-SNAP-058 | OK | — | 256 | 23 | f80a80fc7c880708… | |
| REL-SNAP-059 | OK | — | 260 | 23 | f80a80fc7c880708… |
Tool schema changed 2 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
a2awire.com/mcp/benchmarks/launch-recurring-bill-reconcile-2026-09-17-c9c2481b/http— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.a2awire/benchmark-launch-recurring-bill-reconcile-2026-09-17-c9c2481b 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
- a2awire 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.