https://mcp.cve.now/mcp. It needs no login, OAuth, or API key. Once connected, your agent can look up any vulnerability, read the latest feed, and check the packages in your project against the catalog.
Prerequisites
- A coding agent that supports remote MCP servers over Streamable HTTP, such as Claude Code, Codex, OpenCode, or Cursor.
Add the server
- Claude Code
- Codex
- OpenCode
- Cursor
- Other agents
Run this in your terminal:
Tell your agent when to use it
A connected server only helps if the agent reaches for it. Add this block to your project’sAGENTS.md (Codex, OpenCode, Cursor) or CLAUDE.md (Claude Code), so dependency questions go through cve.now:
Tools and operations
The server has two tools that never change:search finds an operation and execute runs one. Call search with no arguments to list every operation, with a query to narrow them, or with includeInputSchema: true and an operation’s name for its exact arguments. Run one with execute: {"name": "cve.get", "arguments": {"id": "CVE-2021-44228"}}. The data search is the operation entities.search, not the search tool.
An argument an operation does not take answers with an error that lists the ones it does.
The old tools
get_vulnerability, list_feed, check_stack, search (with q), get_leaderboard, get_package and send_feedback are deprecated since 2026-11-11. They still answer as before, but tools/list no longer shows them, and each answer names the operation that replaces it.
feed.read’s filter, tech, and ecosystem work like the feed parameters: each takes one value or a list, an item must match any listed value of a field and every field passed, and at most 16 combinations are allowed.
stack.check accepts the same lockfiles as an upload, and up to 10,000 packages per call. For a large lockfile, have the agent upload it and pass the returned id as stack_id, so the file’s contents do not go through the agent’s context:
Example prompts
- “Use cve.now to check this project’s lockfile for vulnerabilities, and propose upgrades for anything critical.”
- “What’s on the cve.now critical feed today that affects Next.js or React?”
- “Look up CVE-2021-44228 on cve.now. Is it in KEV, and what version fixes it?”
The Sazabi agent
The Sazabi agent has cve.now built in: it is a managed MCP connector that is on by default in every Sazabi project, with nothing to configure. Setup details are on the cve.now connector page.Verify
Ask the agent to look up CVE-2021-44228 on cve.now. Confirm it runscve.get and answers with the Log4Shell entry, including that it is in CISA KEV.