api.tvarka.pro/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-008 | OK | — | 468 | 7 | b26dca921b581790… | |
| REL-SNAP-009 | OK | — | 432 | 7 | 71775b426f30503e… | |
| REL-SNAP-010 | OK | — | 1030 | 7 | 71775b426f30503e… | |
| REL-SNAP-011 | OK | — | 437 | 9 | 56d8891897a1cfdd… | |
| REL-SNAP-012 | OK | — | 1038 | 9 | 56d8891897a1cfdd… | |
| REL-SNAP-013 | OK | — | 462 | 9 | 56d8891897a1cfdd… | |
| REL-SNAP-014 | OK | — | 499 | 9 | 56d8891897a1cfdd… | |
| REL-SNAP-015 | OK | — | 143 | 9 | 56d8891897a1cfdd… | |
| REL-SNAP-016 | OK | — | 146 | 9 | 56d8891897a1cfdd… |
Tool schema changed 2 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
api.tvarka.pro/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- pro.tvarka/due-diligence 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
- Tvarka Due Diligence 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.