a2abench-mcp.web.app/mcp
Last observed:— recorded as TLS_FAIL (post_rejected)
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-003 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-004 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-005 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-006 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-007 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-008 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-009 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-010 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-011 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-012 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-013 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-014 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-015 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-016 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-017 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-018 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-019 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-020 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-021 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-022 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-023 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-024 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-025 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-026 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-027 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-028 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-029 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-030 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-031 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-032 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-033 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-034 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-035 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-036 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-037 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-038 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-039 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-040 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-041 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-042 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-043 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-044 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-045 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-046 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-047 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-048 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-049 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-050 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-051 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-052 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-053 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-054 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-055 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-056 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-057 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-058 | TLS_FAIL | post_rejected | — | — | — | |
| REL-SNAP-059 | TLS_FAIL | post_rejected | — | — | — |
Identity
- Record key
a2abench-mcp.web.app/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.khalidsaidi/a2abench 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
- Not reported. 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.