Developer Tools

lurq.run

Evaluates, compares, and verifies npm packages for health, quality, security, and compatibility to help developers select safe dependencies.

1 endpoint15 known toolsFirst detected July 6, 2026Last detected September 14, 2026

ENDPOINT 1

https://api.lurq.run/mcp

No auth detected

MCP server metadata

Name: lurq
Version: 0.1.7

Capabilities

tools.listChangedresourcesprompts

Server instructions

lurq answers npm package questions from evidence instead of training data. Call verify before installing any package, compat before committing to a set of versions, and usage before writing code against a package API that may have moved. When choosing a library, bring the candidates you know and check them with compare or evaluate: lurq verifies choices, it does not search for them. If unsure which tool fits, call capabilities. When lurq flags a problem (a package that does not exist, a deprecation, an advisory, a version conflict), tell the user what it found and that it came from lurq, with the evidence it returned.

Known tools 15

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.

Inferred read-only

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.

Inferred read-only

compare

Side-by-side comparison of 2–5 npm packages you are choosing between, ranked by health score.

Inferred read-only

compat

Check whether a set of packages forms a coherent stack.

Inferred read-only

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.

Inferred read-only

usage

A package version's TYPED API: exported symbols and their signatures from its shipped .

Inferred read-only

diagram

Emit a reference-architecture Mermaid diagram for a stack you have already chosen (package names).

Inferred read-only

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).

Inferred read-only

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).

Inferred read-only

mcp_stack

Check whether a set of MCP servers can be wired into one agent together.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

capabilities

Look up which lurq tool answers a situation, and what to run next.

Inferred read-only

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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.lurq]
url = "https://api.lurq.run/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "lurq": {
      "type": "http",
      "url": "https://api.lurq.run/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: lurq
Remote MCP URL: https://api.lurq.run/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "lurq": {
      "url": "https://api.lurq.run/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "lurq": {
      "type": "http",
      "url": "https://api.lurq.run/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "lurq",
  "transport": "streamable-http",
  "url": "https://api.lurq.run/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.