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