CVElens Vulnerability Intelligence
com.cvelensPublished by cvelens.comOfficial publisherv0.1.1Updated Oct 24, 2026
CVE triage in one call: NVD, CVSS, CISA KEV, EPSS, public exploits and an explained risk score.
Overview
Lets an assistant look up and triage CVEs, combining NVD, CVSS, CISA KEV, EPSS, public exploit data and an explained risk score in one call.
- What you can do
- CVElens Vulnerability Intelligence is a remote MCP server for vulnerability triage. According to its description, it answers CVE queries in a single call by pulling together NVD data, CVSS severity, CISA KEV status, EPSS scores, public exploit information, and an explained risk score. The manifest lists no individual tools, so the exact tool names and parameters are not documented here.
- When to use it
- Useful when an assistant needs to assess the urgency of a specific CVE, check whether it is known to be exploited, or rank vulnerabilities during patch or security review work. It is aimed at security triage rather than general web search.
- Requirements
- A remote streamable HTTP endpoint at api.cvelens.com; no local package or runtime is needed. Authentication is required via the X-API-Key header, using either a RapidAPI key (free plan: 500 requests per month, paid plans available) or a CVElens key. Network access to the endpoint is required.
Installation
In SourceWeft
- Open CVElens Vulnerability Intelligence in the dashboard and add it to a workspace.
- Connect X-API-Key credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.cvelens%2Fcvelens/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"cvelens-vulnerability-intelligence": {
"type": "http",
"url": "https://api.cvelens.com/mcp",
"headers": {
"X-API-Key": "<YOUR_API_KEY>"
}
}
}
}Tools
0Version history
1- v0.1.1LatestSep 23, 2026
Score
39% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.