Developer tools Sazabi
cve.now API + MCP
Collect vulnerability information through a combined API, feeds and MCP tools, including a dependency lockfile check.
Source review: 2026-10-28 · Imported: 1 November 2026
A practical starting point
What could you build?
A maintenance assistant can look for relevant vulnerability records while reviewing a software project.
Before you connect
Match findings to the actual package version and environment. A record or a clean lookup alone does not prove exploitability or safety.
Capabilities & requirements
Dated specifications from the licensed source dataset. “Not published” indicates missing information, rather than confirmed absence.
| Capability | Details and source |
|---|---|
| Status | Not published No beta or GA label and no SLA. Launched Oct 22, 2026; the MCP server reports version 0.1.0. Source (external) · Not published by vendor: checked 2026-10-28 on https://cve.now/ |
| API key required | No key, no login REST, feeds and MCP all answered HTTP 200 without auth on 2026-10-28. Source (external) · Verified 2026-10-28 by test request to https://cve.now/llms.txt |
| Free tier | Free; no paid tier The FAQ says it is free with no login or key; Sazabi merges the data for its own product. Source (external) · Verified 2026-10-28 on https://cve.now/#faq |
| Rate limit | Not published No numeric limit is published, and the source publisher’s test responses carried no rate-limit headers. Source (external) · Not published by vendor: checked 2026-10-28 on https://github.com/sazabi/cve.now |
| Official MCP server | Hosted, mcp.cve.now/mcp Streamable HTTP, no auth; tools get_vulnerability, list_feed and check_stack (tools/list run 2026-10-28). Source (external) · Verified 2026-10-28 on https://github.com/sazabi/cve.now |
| Official SDK | Not published No SDK is published; the docs describe plain HTTPS endpoints, feeds and MCP. Source (external) · Not published by vendor: checked 2026-10-28 on https://github.com/sazabi/cve.now |
| Data license / terms | Summaries CC BY 4.0; sources keep theirs Upstream data keeps its own license and attribution; NVD data, not endorsed by NVD. No terms page. Source (external) · Verified 2026-10-28 on https://github.com/sazabi/cve.now |
| Commercial use allowed | Not published No terms of service or commercial-use rule is published; CC BY 4.0 on summaries allows commercial reuse with credit. Source (external) · Not published by vendor: checked 2026-10-28 on https://github.com/sazabi/cve.now |
| CORS / browser use | Access-Control-Allow-Origin: * The README says /feed and /api/v1/* send ACAO *; our GET and MCP POST returned it. Source (external) · Verified 2026-10-28 by test request to https://github.com/sazabi/cve.now |
| Freshness / coverage | Minutes; 397,140 entries CVE List, GitHub, OSV and KEV every few minutes, NVD and EUVD every ten; count from /api/stats on 2026-10-28. Source (external) · Verified 2026-10-28 by test request to https://cve.now/api/stats |
Operational reference
Additional facts and qualifications retained from AgentAPIList’s CC BY 4.0 dataset, with provider references.
Price
Free, with no login and no API key. The FAQ says Sazabi already merges this data for its own product, so publishing it costs little.
Provider reference (external)API key / auth
None. The REST endpoints and the MCP server at https://mcp.cve.now/mcp are unauthenticated; our keyless calls on 2026-10-28 returned HTTP 200.
Provider reference (external)Rate limit
No numeric limit is published, and the source publisher’s test responses carried no rate-limit headers.
Provider reference (external)License / terms
Model-written summaries are CC BY 4.0; upstream data keeps its own license and attribution (NVD data, not endorsed by NVD). No separate terms of service page is published.
Provider reference (external)Version status
No beta or GA label. The MCP server reports version 0.1.0, and the site says it launched on Oct 22, 2026.
Provider reference (external)Sources and freshness
CVE List, GitHub advisories, OSV and KEV are checked every few minutes; NVD and EUVD every ten minutes; EPSS changes a few times a day. /api/v1/status showed all eight sources OK on the check date.
Provider reference (external)Coverage
397,140 vulnerabilities tracked on 2026-10-28 (/api/stats). Package matching covers npm, PyPI, Go, Maven, crates.io, Packagist, RubyGems, Hex and NuGet lockfiles.
Provider reference (external)Endpoints
GET /api/v1/entries/<id> (follow redirects), /api/v1/entries (cursor paging, filter=critical,kev), /api/v1/status, /feed with filter, tech and ecosystem, /stack?p=… and POST /api/stack for lockfile upload.
Provider reference (external)Setup references
HTTP request example
Adapted from the attributed source dataset. Review before running; these examples were not executed by Tech in General.
curl -sSL "https://cve.now/api/v1/entries/CVE-2021-44228"Agent connection example
Adapted from the attributed source dataset. Review before running; these examples were not executed by Tech in General.
# Claude Code
claude mcp add --transport http cve-now https://mcp.cve.now/mcp
# Cursor: .cursor/mcp.json
{
"mcpServers": {
"cve-now": { "url": "https://mcp.cve.now/mcp" }
}
}
# Tools: get_vulnerability(id), list_feed(name|filter|tech|ecosystem, limit<=200),
# check_stack(lockfile_content | packages[{ecosystem,name,version}] | stack_id)A tool schema needs an HTTP implementation; it does not by itself install an MCP server. Keep credentials out of browser code.
Other connections to explore
- OSV API (external)
- NVD CVE API 2.0 (external)
- GitLab MCP server (external)
- Official MCP Registry API (external)
- Elliptic Binance hack blocklist (external)
Source & reuse
Download the complete licensed source snapshot (JSON), including the original source’s caveats, alternative notes and examples.