vulnerable.now

Look up vulnerabilities

get_vulnerability

Read-onlyIdempotent

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_vulnerability"
  }
}

Input Schema

Name	Required	Description	Default
`id`	No	One ID, such as CVE-2021-44228, GHSA-jfh8-c2jp-5v3q or PYSEC-2021-19.
`ids`	No	Up to 20 IDs at once, for triaging scanner output.

Output Schema

Name	Required	Description
`error`	No
`missing`	No	IDs no source has published.
`vulnerability`	No	The entry, when one ID was asked for.
`vulnerabilities`	No	The entries found, in the order asked.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish that this is a safe, read-only, idempotent, open-world lookup. Beyond that, the description discloses that entries are merged and previews the returned fields, including CVSS, CISA KEV, EPSS, exploits, affected packages, and fixed versions. It leaves out error behavior and rate-limit context, but adds substantial useful behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tight sentences, front-loads the core action and supported ID types, then summarizes the return payload. Every clause contributes useful information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It covers the essential purpose, accepted identifier families, and key return contents, and the presence of an output schema means return details need not be exhaustive. It does not explain precedence when both id and ids are supplied, or what happens when neither is provided.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema fully documents the id and ids parameters, including examples and the 20-ID limit. The description still adds meaning by broadening the accepted ID namespaces to include EUVD, GO, and RUSTSEC, and by framing the inputs as one or more identifiers for merged lookup.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'Get the merged entry' for vulnerability IDs, and it enumerates CVE, GHSA, EUVD, and OSV-style IDs. It is clear what the tool returns, but it does not explicitly distinguish itself from siblings such as search or get_package.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'one or more IDs' and the accepted ID families, which tells an agent this is an ID-based lookup. The description does not state when to use this instead of search, list_feed, or top_priority, and it gives no exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All vulnerable.now tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?