Model Context Protocol server for lrvx — gives AI agents grounded access to indicators, error codes, and the C API.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"lrvx-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# lrvx-mcp — Model Context Protocol server for lrvx Gives AI agents (Cursor, Claude Code, Cline) **grounded** access to the lrvx C-API surface, error catalog, and indicator library — so they can write code against real signatures instead of guessing. The server runs locally on the developer's machine; the IDE spawns it as a child process and talks to it over stdio. There is no public hosting; nothing leaves the machine. ## Tools | Tool | What it does | |---|---| | `list_indicators` | Every indicator in `lrvx` with class signature, batch fn (if any), and shape. Filter by substring. | | `lookup_error_code` | `E_SYM_001` → full Markdown page with fix recipe, common causes, diagnostics. | | `list_capi_functions` | Search the lrvx C-API surface from the committed ABI snapshot. Returns `name + return type + parameter types`. | | `validate_strategy` | Static-analysis check on Python strategy code: AST parses, expected hooks present, no `eval`/`exec`. | | `explain_event` | Describe the fields of a lrvx event struct (`LrvxTradeData`, `LrvxBookData`, `LrvxBarData`, `LrvxSymbolContext`, `LrvxSignal`). Accepts a struct name or a raw event dict. | | `lookup_symbol` | Take any binding-local spelling (`LrvxBarData`, `BarData`, `lrvx_indicator_ema`, `ema`) and return what the symbol is called in C-API, Python, Node, and Codon. | | `list_bindings` | Enumerate the exports of one binding (capi, python, node, codon, quickjs). Substring filter and limit. | | `get_example` | Code from `docs/examples/` matching a topic (strategy, connector, indicator, event-handler, risk, backtest), optionally filtered by language. | | `scaffold_strategy` | Starter strategy class for Python or Node. Three kinds: bar-driven, trade-driven, hybrid. The Python output goes through `ast.parse` + `validate_strategy`; the Node output goes through `node --check`. CI fails if either breaks, so templates can't quietly rot. | | `docs_search` | Top-k FTS5 search over the docs. The index is built from an allowlist…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.