answeringservicequotes.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-040 | OK | — | 557 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-041 | OK | — | 519 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-042 | OK | — | 557 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-043 | OK | — | 564 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-044 | OK | — | 577 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-045 | OK | — | 854 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-046 | OK | — | 526 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-047 | OK | — | 687 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-048 | OK | — | 770 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-049 | OK | — | 567 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-050 | OK | — | 566 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-051 | OK | — | 549 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-052 | OK | — | 538 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-053 | OK | — | 533 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-054 | OK | — | 534 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-055 | OK | — | 537 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-056 | OK | — | 571 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-057 | OK | — | 550 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-058 | OK | — | 549 | 10 | 78e0c57fbcd158ca… | |
| REL-SNAP-059 | OK | — | 560 | 10 | 78e0c57fbcd158ca… |
Identity
- Record key
answeringservicequotes.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.answeringservicequotes/site 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
- Answering Service Quotes (answeringservicequotes.com) 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.