api.invowerk.dev/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-056 | OK | — | 103 | 6 | 34d8a3db2784f5f1… | |
| REL-SNAP-057 | OK | — | 58 | 6 | 34d8a3db2784f5f1… | |
| REL-SNAP-058 | OK | — | 70 | 6 | 34d8a3db2784f5f1… | |
| REL-SNAP-059 | OK | — | 79 | 6 | 34d8a3db2784f5f1… |
Identity
- Record key
api.invowerk.dev/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- dev.invowerk/invowerk, dev.invowerk/xrechnung-e-invoice-validator 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. — more than one registry name refers to this single endpoint. We record both rather than choosing between them; the observation covers the endpoint and cannot be attributed to one of them.
- Name reported by the server
- invowerk 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.