api.lurq.run/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-041 | OK | — | 348 | 15 | ffa986e8c19f3da3… | |
| REL-SNAP-042 | OK | — | 467 | 15 | ffa986e8c19f3da3… | |
| REL-SNAP-043 | OK | — | 308 | 15 | ffa986e8c19f3da3… | |
| REL-SNAP-044 | OK | — | 279 | 16 | 6205c7706295b72d… | |
| REL-SNAP-045 | OK | — | 310 | 16 | 6205c7706295b72d… | |
| REL-SNAP-046 | OK | — | 323 | 16 | 6205c7706295b72d… | |
| REL-SNAP-047 | OK | — | 245 | 16 | 6205c7706295b72d… | |
| REL-SNAP-048 | OK | — | 335 | 16 | 6205c7706295b72d… | |
| REL-SNAP-049 | OK | — | 314 | 16 | 6205c7706295b72d… | |
| REL-SNAP-050 | OK | — | 238 | 16 | 6205c7706295b72d… | |
| REL-SNAP-051 | OK | — | 254 | 16 | 6205c7706295b72d… | |
| REL-SNAP-052 | OK | — | 399 | 16 | 6205c7706295b72d… | |
| REL-SNAP-053 | OK | — | 367 | 16 | 6205c7706295b72d… | |
| REL-SNAP-054 | OK | — | 326 | 16 | 6205c7706295b72d… | |
| REL-SNAP-055 | OK | — | 372 | 16 | 6205c7706295b72d… | |
| REL-SNAP-056 | OK | — | 496 | 16 | 6205c7706295b72d… | |
| REL-SNAP-057 | OK | — | 323 | 16 | 6205c7706295b72d… | |
| REL-SNAP-058 | OK | — | 350 | 16 | 6205c7706295b72d… | |
| REL-SNAP-059 | OK | — | 246 | 16 | 6205c7706295b72d… |
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
api.lurq.run/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.jadenryu/lurq 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
- lurq 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.