mcp.luxalgo.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-009 | OK | — | 590 | 8 | 7a620f6ff79ccdcc… | |
| REL-SNAP-010 | OK | — | 712 | 8 | 7a620f6ff79ccdcc… | |
| REL-SNAP-011 | OK | — | 588 | 8 | 7a620f6ff79ccdcc… | |
| REL-SNAP-012 | OK | — | 702 | 8 | 7a620f6ff79ccdcc… | |
| REL-SNAP-013 | OK | — | 642 | 8 | 7a620f6ff79ccdcc… | |
| REL-SNAP-014 | OK | — | 603 | 8 | 7a620f6ff79ccdcc… | |
| REL-SNAP-015 | OK | — | 333 | 8 | 7a620f6ff79ccdcc… | |
| REL-SNAP-016 | OK | — | 366 | 8 | 7a620f6ff79ccdcc… | |
| REL-SNAP-017 | OK | — | 401 | 8 | 7a620f6ff79ccdcc… | |
| REL-SNAP-018 | OK | — | 286 | 8 | 7a620f6ff79ccdcc… | |
| REL-SNAP-019 | OK | — | 296 | 8 | 7a620f6ff79ccdcc… | |
| REL-SNAP-020 | OK | — | 274 | 8 | 7a620f6ff79ccdcc… | |
| REL-SNAP-021 | OK | — | 278 | 8 | 7a620f6ff79ccdcc… | |
| REL-SNAP-022 | OK | — | 311 | 8 | 7a620f6ff79ccdcc… | |
| REL-SNAP-023 | OK | — | 276 | 13 | 607da00df6431e93… | |
| REL-SNAP-024 | OK | — | 298 | 21 | 6183ba8288cdbda2… | |
| REL-SNAP-025 | OK | — | 319 | 21 | 6183ba8288cdbda2… | |
| REL-SNAP-026 | OK | — | 409 | 21 | 6183ba8288cdbda2… |
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
mcp.luxalgo.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.LuxAlgo/luxalgo-mcp-server 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
- mcp-typescript server on vercel 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.