mydart.eocpa.kr/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-009 | OK | — | 222 | 16 | 7d908cac2c127f65… | |
| REL-SNAP-010 | OK | — | 200 | 16 | 1a0c7acb7322ca69… | |
| REL-SNAP-011 | OK | — | 269 | 16 | 1a0c7acb7322ca69… | |
| REL-SNAP-012 | OK | — | 224 | 16 | 1a0c7acb7322ca69… | |
| REL-SNAP-013 | OK | — | 260 | 16 | 1a0c7acb7322ca69… | |
| REL-SNAP-014 | OK | — | 282 | 16 | 1a0c7acb7322ca69… | |
| REL-SNAP-015 | OK | — | 684 | 16 | 1a0c7acb7322ca69… | |
| REL-SNAP-016 | OK | — | 1062 | 16 | 1a0c7acb7322ca69… | |
| REL-SNAP-017 | OK | — | 645 | 16 | 1a0c7acb7322ca69… | |
| REL-SNAP-018 | OK | — | 909 | 16 | 1a0c7acb7322ca69… | |
| REL-SNAP-019 | OK | — | 820 | 16 | 1a0c7acb7322ca69… | |
| REL-SNAP-020 | OK | — | 621 | 16 | 1a0c7acb7322ca69… | |
| REL-SNAP-021 | OK | — | 704 | 16 | 1a0c7acb7322ca69… | |
| REL-SNAP-022 | OK | — | 693 | 16 | da18c246061ab29b… | |
| REL-SNAP-023 | OK | — | 714 | 16 | da18c246061ab29b… | |
| REL-SNAP-024 | OK | — | 574 | 16 | 82269b5a6e32f5ce… | |
| REL-SNAP-025 | OK | — | 609 | 16 | 82269b5a6e32f5ce… | |
| REL-SNAP-026 | OK | — | 799 | 16 | 8753bb478eb93c46… |
Tool schema changed 4 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
mydart.eocpa.kr/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- kr.eocpa/mydart 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
- mydart-mcp 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.