lurq
io.github.jadenryu/lurq · v0.1.7 · MCP 2025-11-25
Verify npm packages before your AI agent installs them: hallucinations, advisories, API drift.
Reachability
reachable
checked 2026-09-20 05:32 UTC
Registry status active
Tools pinned 16
be360194f572
Tools last changed
2026-09-17
Repo last push 2026-09-14
GitHub stars 8
Provenance
Registry namespace io.github.jadenryu
(GitHub-account verified by the official registry)
Repository
github.com/jadenryu/lurq
Website
https://www.lurq.run
Remote endpoints
https://api.lurq.run/mcp (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-09-17 05:32 | tools changed | 1 added, 0 removed, 0 changed |
| 2026-09-14 05:30 | first capture | 15 tools pinned |
Pinned tool definitions (16)
| Tool | Description |
|---|---|
| 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... |
| 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... |
| 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`. |
| 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... |
| 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.... |
| 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... |
| 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. |
| 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... |
| 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).... |
| 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... |
| 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... |
| 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... |
| 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,... |
| 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... |
| 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.... |
| 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... |
Get alerted when this changes.
Email the moment io.github.jadenryu/lurq drifts, dies, or revives.
Status badge
[](https://toolpin.dev/servers/io.github.jadenryu/lurq)
Maintain this server? Add the badge to your README. It links your users to this live status page.