lurq is a remote MCP server that gives an AI agent 16 tools, among them audit, capabilities, compare. It answers at https://api.lurq.run/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 5 of 5 times since 13 September 2026; the last check, on 23 October 2026, succeeded.
Verify npm packages before your AI agent installs them: hallucinations, advisories, API drift.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
audit | Assess an entire project's dependencies in ONE call: which packages are outdated, deprecated or carry advisories for the exact installed version, and which configured MCP servers have drifted, need credentials, or cannot be observed at all. Inputs: packages, mcpServers |
capabilities | Look up which lurq tool answers a situation, and what to run next. Call when you're unsure whether lurq covers something (an upgrade, a licence rule, a version's exact exports, publishing a package) instead of guessing or skipping it. Retur Inputs: query |
compare | Side-by-side comparison of 2–5 npm packages you are choosing between, ranked by health score. Untracked names are fetched on demand; one still being scored comes back under `pending` (retry shortly), and a name not on npm under `notFound`. Inputs: packages |
compat | Check whether a set of packages forms a coherent stack. Resolves the whole set the way npm would and returns a definitive verdict: compatible, conflict (with the exact clashing constraints), or unknown. Checks peer-dependency and engine ran Inputs: packages, versions, node |
connect_check | Before wiring an MCP server into a client, find out whether it will work there and exactly what it takes. Accepts an endpoint URL, an official-registry server name, or an npm package name. Answers per client (Claude Code, Claude.ai, ChatGPT Inputs: server, client |
diagram | Emit a reference-architecture Mermaid diagram for a stack you have already chosen (package names). A labeled starting point keyed by layer, not a validated architecture, and not an architecture designer. Inputs: stack |
diff_surface | What changed in a package's runtime surface between two versions: symbols removed, added, and arity changes, plus renames the package itself proves (a removed name that shared one declaration with a name the new version still exports). Remo Inputs: package, fromVersion, toVersion |
evaluate | Full evidence read for one npm package: health and quality scores and the signals behind them, advisories, the shared safety verdict, a summary and a usage guide. Use it when a choice needs more than verify's install gate. Enforces the acco Inputs: package |
mcp_drift | What moved in an MCP server's tool contract between two versions: tools removed, parameters that became required, types narrowed, and annotation flips. Two findings here have no npm equivalent and are why this exists. SILENT DRIFT is a sche Inputs: server, fromVersion, toVersion |
mcp_stack | Check whether a set of MCP servers can be wired into one agent together. The npm question does not apply — servers are separate processes with nothing to resolve between them. They clash in the single flat TOOL NAMESPACE the agent assembles Inputs: servers |
mcp_surface | What an MCP server ACTUALLY exposes: every tool, its required and optional parameters, and its behaviour annotations, read from a live `tools/list` handshake in a sandbox rather than from a README or the model's memory. Call before wiring a Inputs: server, version |
policy | The rules this account's selection policy enforces on which packages you may add: denied packages (with the reason), license allowlist, confidence, advisory, adoption, staleness and bundle-size floors. Read it once before choosing dependenc |
report_outcome | Opt-in feedback after you act on lurq's evidence about a package (verify, evaluate, compare, compat): whether you went with it and whether it built. No source code, only the coarse decision + a build signal. Helps lurq learn which packages Inputs: package, accepted, buildSignal, need |
resolve_surface | What a package version ACTUALLY exports at runtime, extracted from its shipped JavaScript rather than from documentation or the model's memory: names and arity, not type signatures (use usage for those). Call before writing code against a p Inputs: package, version |
usage | A package version's TYPED API: exported symbols and their signatures from its shipped .d.ts (or DefinitelyTyped), exact to the version, none of it in the model's training data. Use before writing code against a package whose API may have mo Inputs: package, version, knownVersion, query, offset |
verify | Confirm an npm package is real, healthy, and not risky before installing: guards against hallucinated or typosquatted names, deprecations and known advisories, and returns a safety verdict with its reasons and what was not checked. Checks t Inputs: package |
Every block below points at https://api.lurq.run/mcp. Pick your client and copy.
claude mcp add --transport http lurq https://api.lurq.run/mcp
{
"mcpServers": {
"lurq": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.lurq.run/mcp"]
}
}
}{
"mcpServers": {
"lurq": {
"url": "https://api.lurq.run/mcp"
}
}
}{
"servers": {
"lurq": {
"type": "http",
"url": "https://api.lurq.run/mcp"
}
}
}{
"context_servers": {
"lurq": {
"url": "https://api.lurq.run/mcp"
}
}
}{
"mcpServers": {
"lurq": {
"serverUrl": "https://api.lurq.run/mcp"
}
}
}{
"mcpServers": {
"lurq": {
"url": "https://api.lurq.run/mcp"
}
}
}name: lurq
version: 0.0.1
schema: v1
mcpServers:
- name: lurq
type: streamable-http
url: https://api.lurq.run/mcp{
"mcpServers": {
"lurq": {
"httpUrl": "https://api.lurq.run/mcp"
}
}
}{
"mcpServers": {
"lurq": {
"type": "http",
"url": "https://api.lurq.run/mcp"
}
}
}{
"mcpServers": {
"lurq": {
"url": "https://api.lurq.run/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.lurq.run%2Fmcp&type=streamable_http&id=lurq&name=lurq
It answered our last check on 23 October 2026 in 319 ms. Over 5 checks since 13 September 2026 it answered 5. Status here comes from Neuronto's own probes, not from the publisher.
16, as returned by the server's own tools/list on 24 September 2026: audit, capabilities, compare, compat, connect_check, diagram, diff_surface, evaluate, and 8 more.
It answered our last check on 23 October 2026 in 319 ms. Over 5 checks since 13 September 2026 it answered 5.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.lurq.run/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.jadenryu. Endpoint host: api.lurq.run. ARD identifier: urn:air:io.github.jadenryu:mcp:lurq.
First indexed 13 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.