www.licium.ai/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 603 | 11 | a0a438dd32e2a89c… | |
| REL-SNAP-003 | OK | — | 614 | 11 | a0a438dd32e2a89c… | |
| REL-SNAP-004 | OK | — | 619 | 12 | abc1c05bdbf3db9c… | |
| REL-SNAP-005 | OK | — | 589 | 12 | abc1c05bdbf3db9c… | |
| REL-SNAP-006 | OK | — | 862 | 15 | 30b4c880d1429363… | |
| REL-SNAP-007 | OK | — | 665 | 15 | 30b4c880d1429363… | |
| REL-SNAP-008 | OK | — | 699 | 15 | 30b4c880d1429363… | |
| REL-SNAP-009 | OK | — | 581 | 15 | 30b4c880d1429363… | |
| REL-SNAP-010 | OK | — | 625 | 23 | 7b357a8585baaaf4… | |
| REL-SNAP-011 | OK | — | 591 | 23 | 7b357a8585baaaf4… | |
| REL-SNAP-012 | OK | — | 623 | 26 | c63716cfd4dd89ff… | |
| REL-SNAP-013 | OK | — | 601 | 26 | 66ade575981fe5d3… | |
| REL-SNAP-014 | OK | — | 611 | 26 | 66ade575981fe5d3… | |
| REL-SNAP-015 | OK | — | 318 | 26 | 66ade575981fe5d3… | |
| REL-SNAP-016 | OK | — | 339 | 26 | 66ade575981fe5d3… | |
| REL-SNAP-017 | OK | — | 304 | 26 | 66ade575981fe5d3… | |
| REL-SNAP-018 | OK | — | 431 | 26 | 66ade575981fe5d3… | |
| REL-SNAP-019 | OK | — | 347 | 26 | 66ade575981fe5d3… | |
| REL-SNAP-020 | OK | — | 305 | 26 | 66ade575981fe5d3… | |
| REL-SNAP-021 | OK | — | 332 | 26 | 66ade575981fe5d3… | |
| REL-SNAP-022 | OK | — | 370 | 26 | 66ade575981fe5d3… | |
| REL-SNAP-023 | OK | — | 317 | 26 | 66ade575981fe5d3… | |
| REL-SNAP-024 | OK | — | 358 | 26 | 66ade575981fe5d3… | |
| REL-SNAP-025 | OK | — | 328 | 26 | 66ade575981fe5d3… | |
| REL-SNAP-026 | OK | — | 291 | 26 | 66ade575981fe5d3… |
Tool schema changed 5 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
www.licium.ai/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.Licium-ai/licium 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
- licium 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.