Skip to content
Vulnrable logo

Vulnrable MCP server

Which MCP servers are Vulnrable's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-21

← Back to Vulnrable

Whose server it is
  • Registry namecom.vulnrable/vulnrableverified in the MCP registry

The registry name sits under vulnrable.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-21
  • Stateanswerschecked 2026-10-21
  • Tools4
  • Server calls itselfvulnrable
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 363 ms.

Should an agent connect itConnect it
  • Its tools do every use case we checked: compare third-party package counts across MCP servers; check packages against known vulnerability databases.

Once connected

  • For "compare third-party package counts across MCP servers", the likely first call is list_mcp_servers.
  • For "check packages against known vulnerability databases", the likely first call is check_package.
  • Parameters are untyped or undescribed in 2 of 4 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 7, the first on 2026-10-21
  • INITE MCP score94 of 100answers 100 · does the job 100 · definitions 75 · context 100 · connects 100
  • What an agent can do with it2 of 2 use cases
  • Answered100% of days7 of 7 daily checks
  • Median first answer509 ms
  • Space in an agent's context≈ 470 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsB · 75 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 2 of 4
  • Not saying whether it only reads or can destroy: 4 of 4

What an agent can do with it

  • can do · compare third-party package counts across MCP servers
  • not sure · browse recent CVEs, exploits and security news
  • can do · check packages against known vulnerability databases

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-21
  • check_package

    Security assessment of one npm or PyPI package: letter grade, findings, known vulnerabilities, deprecation status, and — for MCP servers in our directory — the real resolved dependency count. Use before recommending or installing a package.

  • list_mcp_servers

    The MCP server directory with real resolved dependency counts. Use when recommending an MCP server, or to compare how much third-party code candidates pull into the agent. For a graded security assessment of one server, call check_package.

  • check_cve

    Details for one CVE or GHSA identifier, including whether CISA lists it as actively exploited (KEV) and its EPSS exploitation probability. Use to judge real-world urgency.

  • latest_vulns

    Recently published vulnerabilities from the tracked pool, ranked KEV-first then by EPSS. Use for "what should I worry about this week".

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "vulnrable": {
      "type": "http",
      "url": "https://vulnrable.com/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http vulnrable https://vulnrable.com/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://vulnrable.com/api/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.