vulnerable.now

List recent vulnerabilities

list_feed

Read-onlyIdempotent

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.

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": "list_feed"
  }
}

Input Schema

Name	Required	Description
`kev`	No	Only entries in the CISA KEV catalog.
`tech`	No	Only entries naming this vendor or vendor product, as a slug: apache, or apache/tomcat.
`limit`	No
`query`	No	Words to match against IDs, titles, vendors, products and descriptions. For best-match ordering, use search.
`since`	No	Only entries published on or after this date (YYYY-MM-DD).
`until`	No	Only entries published before this date (YYYY-MM-DD).
`cursor`	No	next_cursor from the previous page.
`vendor`	No	Exact vendor name, such as apache or microsoft.
`package`	No	Only entries naming this package, as ecosystem:name, such as npm:lodash or pypi:django.
`product`	No	Exact product name, such as log4j or exchange server.
`severity`	No	Only these severities.
`ecosystem`	No	Package ecosystem, such as npm, PyPI, Maven, Go or crates.io.
`exploited`	No	Only entries with reported exploitation (KEV, CISA SSVC, ENISA or VulnCheck KEV).
`fix_available`	No	Only entries with a fixed version.
`modified_since`	No	Only entries whose merged record changed at or after this date (YYYY-MM-DD) or time (ISO 8601). Pass the newest modified value from the previous run.
`public_exploit`	No	Only entries with public exploit code.

Output Schema

Name	Required	Description
`error`	No
`next_cursor`	No	Pass as cursor, with the same arguments, for the next page.
`vulnerabilities`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

changedInput schema / properties / exploited / description

Previous value: -"Only entries with reported exploitation (KEV, CISA SSVC or ENISA)."New value: +"Only entries with reported exploitation (KEV, CISA SSVC, ENISA or VulnCheck KEV)."

First observedNov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still contributes real behavior beyond that: default result ordering is newest-first and the sort key changes to KEV date-added when kev is set, which an agent cannot learn from the annotations alone. It does not discuss pagination limits or result volume, which is the main remaining gap.

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

Conciseness4/5

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

Two sentences, front-loaded with the operation and ordering before the filter inventory. The filter list is somewhat redundant with the schema and could be trimmed, but it functions as a fast orientation scan for a 16-parameter tool and nothing is padded.

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?

With an output schema present and near-complete parameter documentation, the description only needs to cover what structured fields cannot: ordering behavior and the incremental-sync pattern, both of which are addressed. Cursor-based pagination is left to the schema, which is acceptable, though a brief note that results are paginated would have closed the loop.

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

Parameters3/5

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

Schema description coverage is 94% across 16 parameters, so the schema already carries the semantics and a baseline of 3 applies. The description's filter enumeration (severity, KEV, exploitation, public exploit code, fix availability, ecosystem, vendor, product, text, dates) largely restates categories the schema documents in more detail, and the modified_since advice duplicates the parameter's own description.

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?

States a specific verb and resource ("List vulnerabilities") plus the ordering contract ("newest first", with KEV listings ordered by date added when kev is set). That ordering nuance helps separate it from a relevance-ranked tool, but the description never names or contrasts a sibling, leaving the agent to infer that distinction from the schema's query note.

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?

One concrete usage hint is present: "Use modified_since to pick up changes since a previous run," which tells the agent about an incremental-polling pattern. Beyond that there is no when-to-use versus when-not guidance and no mention of when search or top_priority would be the better call, so the browsing use case is only implied.

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?