agent.milotche.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-042 | OK | — | 544 | 7 | 582f71fb7ba3799e… | |
| REL-SNAP-043 | OK | — | 545 | 7 | 582f71fb7ba3799e… | |
| REL-SNAP-044 | OK | — | 581 | 7 | 9e9ecc8b807fafaf… | |
| REL-SNAP-045 | OK | — | 512 | 7 | 9e9ecc8b807fafaf… | |
| REL-SNAP-046 | OK | — | 542 | 7 | 9e9ecc8b807fafaf… | |
| REL-SNAP-047 | OK | — | 553 | 7 | 9e9ecc8b807fafaf… | |
| REL-SNAP-048 | OK | — | 566 | 7 | 9e9ecc8b807fafaf… | |
| REL-SNAP-049 | OK | — | 574 | 7 | 9e9ecc8b807fafaf… | |
| REL-SNAP-050 | OK | — | 520 | 7 | 9e9ecc8b807fafaf… | |
| REL-SNAP-051 | OK | — | 632 | 7 | 9e9ecc8b807fafaf… | |
| REL-SNAP-052 | OK | — | 560 | 7 | 9e9ecc8b807fafaf… | |
| REL-SNAP-053 | OK | — | 498 | 7 | 9e9ecc8b807fafaf… | |
| REL-SNAP-054 | OK | — | 581 | 7 | 9e9ecc8b807fafaf… | |
| REL-SNAP-055 | OK | — | 584 | 7 | 9e9ecc8b807fafaf… | |
| REL-SNAP-056 | OK | — | 533 | 7 | 9e9ecc8b807fafaf… | |
| REL-SNAP-057 | OK | — | 537 | 7 | 9e9ecc8b807fafaf… | |
| REL-SNAP-058 | OK | — | 659 | 7 | 9e9ecc8b807fafaf… | |
| REL-SNAP-059 | OK | — | 651 | 7 | 9e9ecc8b807fafaf… |
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
agent.milotche.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.milotche/carre-de-sable 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
- carre-de-sable 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.