mcp.takident.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-009 | OK | — | 66 | 12 | 0f43c1d3aa3aa6e6… | |
| REL-SNAP-010 | OK | — | 120 | 12 | 0f43c1d3aa3aa6e6… | |
| REL-SNAP-011 | OK | — | 70 | 12 | fbe2ee7e5c21bb46… | |
| REL-SNAP-012 | OK | — | 127 | 12 | fbe2ee7e5c21bb46… | |
| REL-SNAP-013 | OK | — | 62 | 12 | fbe2ee7e5c21bb46… | |
| REL-SNAP-014 | OK | — | 80 | 12 | fbe2ee7e5c21bb46… | |
| REL-SNAP-015 | OK | — | 696 | 12 | fbe2ee7e5c21bb46… | |
| REL-SNAP-016 | OK | — | 556 | 12 | fbe2ee7e5c21bb46… | |
| REL-SNAP-017 | OK | — | 234 | 12 | fbe2ee7e5c21bb46… | |
| REL-SNAP-018 | OK | — | 657 | 12 | fbe2ee7e5c21bb46… | |
| REL-SNAP-019 | OK | — | 625 | 12 | fbe2ee7e5c21bb46… | |
| REL-SNAP-020 | OK | — | 658 | 12 | fbe2ee7e5c21bb46… | |
| REL-SNAP-021 | OK | — | 614 | 12 | fbe2ee7e5c21bb46… | |
| REL-SNAP-022 | OK | — | 753 | 12 | fbe2ee7e5c21bb46… | |
| REL-SNAP-023 | OK | — | 113 | 12 | fbe2ee7e5c21bb46… | |
| REL-SNAP-024 | OK | — | 106 | 12 | fbe2ee7e5c21bb46… | |
| REL-SNAP-025 | OK | — | 658 | 12 | fbe2ee7e5c21bb46… | |
| REL-SNAP-026 | OK | — | 499 | 12 | fbe2ee7e5c21bb46… |
Tool schema changed 1 time 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
mcp.takident.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.takident/patient-services 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
- Taki Dent Patient Services 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.