Skip to content

lurq MCP server

io.github.jadenryu/lurqjadenryustreamable-httpv0.1.7Scanned

Verify npm packages before your AI agent installs them: hallucinations, advisories, API drift.

16 tools: 13 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 13 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 10
  • Can send data out · 0
  • 4 findings, 1 high

Tools listed without sign-in. Remote posture

With Anlyon

13 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the lurq MCP server can do

The lurq MCP server is published by the GitHub account jadenryu. It has 16 tools. It can create or change data (13 tools: evaluate, policy, compat, verify and 9 more), but cannot delete data. 3 tools only read.

10 tools bring in text other people can write (evaluate, compare, compat and 7 more).

The fixed checks matched 4 findings, 1 of them high severity (annotation-conflict, credentials-mention and sensitive-path). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 0.1.7.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

16 tools

Changes things 13Claude Code: ask
  • auditAssess 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 h…Reads text others write2 findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...nfigured MCP servers have drifted, need credentials, or cannot be observed at all. Send the..."

      What this check looks for
    • High

      The input schema at properties.mcpServers.description refers to ".mcp.json".

      Matched text

      inputSchema.properties.mcpServers.description: "MCP servers read from .mcp.json / agent configs"

      What this check looks for
    Description, as the server wrote it
    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. Send the inventory you read locally (names and versions only — never source). Returns a per-item verdict plus an explicit coverage count: how many were answered, how many are queued because the index has not seen them, and how many were skipped and why. An item lurq could not assess is reported as unassessed, never as clean.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • capabilitiesLook up which lurq tool answers a situation, and what to run next.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Returns matching capabilities with the tool or command to use.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • compatCheck whether a set of packages forms a coherent stack.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 ranges from declared metadata, plus any recorded sandbox conflicts. Read-only: never installs or executes package code. Not always instant: a set checked before answers immediately, but a new set is resolved live from registry metadata, which can take up to ~25 seconds. Call once with the whole stack before committing to it.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • connect_checkBefore wiring an MCP server into a client, find out whether it will work there and exactly what it takes.Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...e fact is not established. Built from a credential-free probe of the endpoint (whether it..."

      What this check looks for
    Description, as the server wrote it
    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, Cursor, VS Code, Codex, Gemini CLI and more): WORKS; NEEDS_SETUP with the steps (a key to send as a header, an OAuth client to pre-register and the redirect URIs to allow, a URL placeholder to fill); BLOCKED with the reason and which side causes it; or UNKNOWN when a decisive fact is not established. Built from a credential-free probe of the endpoint (whether it answers, how it authenticates, which OAuth registration methods it offers, spec deviations strict clients refuse, tool names and schemas) and from primary-sourced client constraints. Returns ready-to-paste config in each client's own format, with placeholder values. Tell the user what it found, including which client it was checked for. UNKNOWN never means it will not work.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • diagramEmit a reference-architecture Mermaid diagram for a stack you have already chosen (package names).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • evaluateFull 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.Reads text others write1 finding

    Why it is in this group

    • The name "evaluate" says "evaluate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "evaluate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "evaluate" says "evaluate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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 account's dependency policy. A package lurq has never tracked is fetched and scored on demand, waiting up to ~4 seconds; if scoring takes longer the result is `tracked: false` with a note to retry in a few seconds, which is not an answer about the package.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • mcp_driftWhat moved in an MCP server's tool contract between two versions: tools removed, parameters that became required, types narrowed, and annotation flips.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 schema that changed while its description stayed byte-identical, invisible to anyone reading a changelog. PRIVILEGE WIDENING is a tool that stopped being read-only or started being destructive, which does not break anything and is worse than a break. Use before upgrading a server an agent depends on.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • mcp_stackCheck whether a set of MCP servers can be wired into one agent together.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 from all of them: two servers exposing the same tool name leave the agent unable to express which it means, and nothing errors, one simply shadows the other. Also reports the standing context cost, since every tool's schema rides in every request. Pass `tools` for a server when you already hold its tool list (any server: remote, PyPI, Docker, private) and it is analysed as-is; otherwise the npm server's probed surface is used, and one that has not been probed makes the answer UNKNOWN, never clean.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • mcp_surfaceWhat 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 th…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 an agent to a server, or when a tool call is failing for reasons the error does not explain. Also returns `requires` — the API keys and settings the server declares it needs — and `configRequest`, a ready-made line to put in front of your user when something is missing, so 'it needs a token' never presents as 'it is broken'. A miss returns UNKNOWN and queues a probe; UNKNOWN never means the server has no tools.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • policyThe rules this account's selection policy enforces on which packages you may add: denied packages (with the reason), license allowlist, confidence, advisory, adoption, staleness an…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 dependencies so you pick an allowed package first; evaluate already enforces it. Read-only.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • report_outcomeOpt-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 findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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 agents actually succeed with; safe to skip.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • usageA 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 moved. For whether a name exists at RUNTIME (what decides if an import throws) use resolve_surface; for is-it-safe-to-install use verify. Pass knownVersion (e.g. the version you were trained on) to get the precise delta: added, removed, renamed, changed. Also returns the version's declared engines (Node/runtime floor). Large surfaces are paged, 80 symbols per call: `totalSymbols` is the size, `query` filters by name, `offset` pages. `shallow: true` means the API lives on an interface's members that are not listed, and the note says where to read them. For framework file/convention changes (not exported symbols), consult the official migration guide / Context7 instead.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • verifyConfirm 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…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 the live registry. The cheap gate to call before every install; use evaluate when you need the full scores.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • compareSide-by-side comparison of 2–5 npm packages you are choosing between, ranked by health score.Reads text others writeNo findings

    Why it is in this group

    • The name "compare" says "compare": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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`.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • diff_surfaceWhat 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 …Reads text others writeNo findings

    Why it is in this group

    • The name "diff_surface" says "diff": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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). Removals break `node`; type-only removals are returned separately because they break `tsc` instead. Answers "when did this stop working" from static comparison, with no install required. Use before an upgrade, and to explain a break after one.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • resolve_surfaceWhat 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…Reads text others writeNo findings

    Why it is in this group

    • The name "resolve_surface" says "resolve": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 package whose API may have moved. Runtime existence is what decides whether an import throws; a removed type breaks tsc, a removed runtime symbol breaks the program. A miss returns UNKNOWN and queues extraction, UNKNOWN never means the symbol is absent.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write10
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:06 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
13
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 13 tools that change things (13 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.lurq.run/mcp: tools/list returned 16 tools to an anonymous client, including evaluate (write), policy (write), compat (write), verify (write), usage (write) and 8 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 high1 warn2 info
  • Highaudit

    The input schema at properties.mcpServers.description refers to ".mcp.json".

    Matched text

    inputSchema.properties.mcpServers.description: "MCP servers read from .mcp.json / agent configs"

    What this check looks for
  • The server marks "evaluate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "evaluate" says "evaluate": a word for a change.

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...e fact is not established. Built from a credential-free probe of the endpoint (whether it..."

    What this check looks for
  • Infoaudit

    The description mentions "credentials".

    Matched text

    description: "...nfigured MCP servers have drifted, need credentials, or cannot be observed at all. Send the..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.7. Values in angle brackets are yours to fill in.

claude mcp add --transport http lurq https://api.lurq.run/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http lurq https://api.lurq.run/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__lurq__compare",
      "mcp__lurq__resolve_surface",
      "mcp__lurq__diff_surface"
    ],
    "ask": [
      "mcp__lurq__evaluate",
      "mcp__lurq__policy",
      "mcp__lurq__compat",
      "mcp__lurq__verify",
      "mcp__lurq__usage",
      "mcp__lurq__diagram",
      "mcp__lurq__mcp_stack",
      "mcp__lurq__mcp_surface",
      "mcp__lurq__mcp_drift",
      "mcp__lurq__connect_check",
      "mcp__lurq__audit",
      "mcp__lurq__capabilities",
      "mcp__lurq__report_outcome"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lurq. Review it before you use it.

Capability tags behind 10 rules
  • mcp__lurq__evaluate untrusted-input
  • mcp__lurq__compare untrusted-input
  • mcp__lurq__compat untrusted-input
  • mcp__lurq__verify untrusted-input
  • mcp__lurq__usage untrusted-input
  • mcp__lurq__resolve_surface untrusted-input
  • mcp__lurq__diff_surface untrusted-input
  • mcp__lurq__mcp_surface untrusted-input
  • mcp__lurq__connect_check untrusted-input
  • mcp__lurq__audit untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.jadenryu/lurq/verify?hash=3cc88a6b637e318b2ad84c9cb0c77d5b7a51f0b447e9ca97dd8a6f2e03bc2e68" | jq -e '.changed == false'

Pinned hash 3cc88a6b637e, from Nov 19, 2026, 22:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.jadenryu/lurq/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.jadenryu/lurq
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.jadenryu/lurq.svg)](https://radar.anlyon.com/servers/io.github.jadenryu/lurq)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:36 UTC.

lurq MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the lurq MCP server safe?

No scan can promise that. What its definitions show: 16 tools, 13 of which can change, send or delete something, and 4 findings (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the lurq MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the lurq MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the lurq MCP server have?

16 tools: 13 write, 3 read. evaluate, policy, compat, verify, usage, diagram, mcp_stack, mcp_surface and 8 more.

Does the lurq MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the lurq MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the lurq MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.