vulnerable.now MCP Server

by vulnerable Your server? Claim it

answering

vulnerable.now is answering right now. Last checked 15 min ago. It exposes 8 tools.

Free CVE lookups, package checks and patch priorities from public sources. No account or API key.

Uptime history 33 hours of history

33 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

553 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 November 2026. No other catalogue keeps this.

11 Nov a tool appeared get_poc

11 Nov a tool changed version

Nothing serious here today

Today is the operative word: we check vulnerable.now every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://vulnerable.now/mcp

Settings → Connectors → Add custom connector, then paste this address

https://vulnerable.now/mcp

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://vulnerable.now/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://vulnerable.now/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://vulnerable.now/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

feed

list_feed

List vulnerabilities newest first (KEV listings by date added when kev is set). Filter by severity, CISA KEV, exploitation, public exploit code, fix availability, ecosystem, vendor, product, text and dates. Use modified_since to pick up changes since a previous run.

package

get_package

Every known vulnerability in one open source package, most urgent first, with the affected ranges and fixed versions published for that package. Give a version to learn which advisories affect it and the lowest upgrade that leaves every affecting range.

poc

get_poc

List the public exploit code and proofs of concept the sources link to one vulnerability: Metasploit exploit modules, Exploit-DB entries, references NVD or the CNA tagged as exploits (broken links left out), and GitHub PoC repositories (most stars first). Links only; nothing is downloaded or run. The same JSON as GET /api/v1/entries/{id}/pocs. GitHub PoCs and tagged references are unverified third-party code, and stars are popularity, not review.

product

get_product

Every known vulnerability in one vendor product, such as an operating system, browser, server, CMS or appliance, most urgent first, with the affected versions and fixes. The vendor is optional: with only a product name, a clear match is answered directly and otherwise the candidates are listed. Give a version to learn which entries affect it and the lowest upgrade that clears them.

search

Search the whole catalog by words: product, vendor, package, CVE ID, common vulnerability name, research metadata or description text. Best match first by default. Each result says which fields matched. When nothing matches, the reply suggests a broader query.

stack

check_stack

Find known vulnerabilities in what a project or site runs, ranked by what to fix first. Send exact package versions, the raw content of a lockfile (package-lock.json, poetry.lock, go.sum and others), a CycloneDX or SPDX SBOM, a Wappalyzer export, or detected technologies such as nginx 1.18.0. Returns each finding with severity, exploitation, priority and fixed versions.

top

top_priority

What to patch first: the vulnerabilities with the highest priority score (exploitation, EPSS, CVSS, automatability) among those with activity in a time window, optionally narrowed to an ecosystem, vendor or product.

vulnerability

get_vulnerability

Get the merged entry for one or more IDs: CVE, GitHub advisory (GHSA), EUVD, or an OSV ID such as PYSEC, GO or RUSTSEC. Returns the description, CVSS, CISA KEV status, EPSS, public exploits, affected packages, fixed versions, priority and source links.

Endpoints

URL	Transport	State	Latency	Checked
https://vulnerable.now/mcp	streamable-http	answering	486 ms	15 min ago

Alternatives to vulnerable.now

same job, measured the same way

Osv MCP

by mrfentmen

MCP server for OSV open source vulnerability data and package security checks.

152 installs/wk local only

overflo.ws

by overflo

Look up CVEs, CISA KEV, EPSS and open-source package vulnerabilities, including malicious packages.

7 tools answering

Package Health Check

by openkrill

Check an npm or Python package, or a package.json, for vulnerabilities and upkeep.

6 tools answering

Dependency Vulnerability Check (OSV)

by brunckel

Known vulnerabilities and fixed versions for npm, PyPI, Go, Maven packages from OSV.dev via Apify.

answering

NPMScan

by salemalem

Detect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups

23 tools answering

UK Data: CVEs and package popularity

by co-reliness

Software vulnerabilities (CVEs) from the US NVD and package downloads for npm, PyPI and crates

4 tools answering

OSV Advisories

by basitalisandhu

Query OSV.dev for known vulnerabilities by package and version, and scan lockfiles in batch.

local only

Dependency check

by ladanyin

Check a package version for known vulnerabilities and Packagist release facts.

2 tools answering

vulnerable.now — questions

Answers built from our own checks of this server.

What can vulnerable.now do?

It exposes 8 tools, read directly from the server on our last check. Among them: check_stack, get_package, get_poc, get_product, get_vulnerability, list_feed and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is vulnerable.now working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 553 ms. The bar chart above shows every period we have measured.

How do I connect vulnerable.now?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does vulnerable.now need an API key?

No. vulnerable.now completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is vulnerable.now?

It answers our handshake in 553 ms on average, which is faster than 21% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.