INDIVIDUAL MCP TOOL
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.
LIVE ENDPOINT
https://vulnerable.now/mcp
Connect to this endpoint to inspect the live schema for top_priority and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
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.vulnerable-now]
url = "https://vulnerable.now/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vulnerable-now": {
"type": "http",
"url": "https://vulnerable.now/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vulnerable-now
Remote MCP URL: https://vulnerable.now/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": {
"vulnerable-now": {
"url": "https://vulnerable.now/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vulnerable-now": {
"type": "http",
"url": "https://vulnerable.now/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vulnerable-now",
"transport": "streamable-http",
"url": "https://vulnerable.now/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
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.search— Search the whole catalog by words: product, vendor, package, CVE ID, common vulnerability name, research metadata or description text.get_package— Every known vulnerability in one open source package, most urgent first, with the affected ranges and fixed versions published for that package.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.list_feed— List vulnerabilities newest first (KEV listings by date added when kev is set).check_stack— Find known vulnerabilities in what a project or site runs, ranked by what to fix first.