CVE, CVSS, EPSS, KEV, exploit, PoC, MITRE, package-advisory, malware, and IP-reputation data can be stale, incomplete, provider-specific, or false positive., Treat generated risk scores and vulnerability reports as triage aids, not patch policy, incident-response authority, or compliance evidence by themselves., Some tools can submit or query URLs, IP addresses, domains, file hashes, package names, repository search terms, and exploit indicators against third-party services., Shodan, URLScan, VirusTotal, AbuseIPDB, GreyNoise, CIRCL, GitHub, VulnCheck, NVD, OSV, and other providers may apply rate limits, visibility rules, account terms, and retention policies., Review provider defaults before scanning URLs or infrastructure because some services can expose submitted targets or scan metadata publicly., The project documentation says the server uses outbound HTTPS only and blocks private/internal IP lookups, but users should still avoid unauthorized reconnaissance or sensitive internal target submission.
Privacy notes
Security queries can reveal vulnerable products, internal triage priorities, asset names, IP addresses, domains, URLs, file hashes, package versions, malware interests, and investigation targets to upstream APIs., API keys are loaded from environment variables; keep them scoped, rotated, and out of model transcripts, shell history, and shared configuration files., The implementation initializes a local SQLite cache and rotating audit log, which can retain query parameters, statuses, timings, source results, and security-investigation context., Audit logging redacts fields whose names include key or token, but other query values can still be sensitive and should be protected as security data., The repository license file is Apache-2.0 while the README badge and pyproject classifier currently mention MIT, so verify current licensing before redistribution or commercial reuse.
Author
Mahipal Jangra
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
6 safety and 5 privacy notes across 6 risk areas. Review closely: credentials & tokens, permissions & scopes, third-party handling.
6 areas
SafetyThird-party handlingCVE, CVSS, EPSS, KEV, exploit, PoC, MITRE, package-advisory, malware, and IP-reputation data can be stale, incomplete, provider-specific, or false positive.
SafetyGeneralTreat generated risk scores and vulnerability reports as triage aids, not patch policy, incident-response authority, or compliance evidence by themselves.
SafetyThird-party handlingSome tools can submit or query URLs, IP addresses, domains, file hashes, package names, repository search terms, and exploit indicators against third-party services.
SafetyThird-party handlingShodan, URLScan, VirusTotal, AbuseIPDB, GreyNoise, CIRCL, GitHub, VulnCheck, NVD, OSV, and other providers may apply rate limits, visibility rules, account terms, and retention policies.
SafetyThird-party handlingReview provider defaults before scanning URLs or infrastructure because some services can expose submitted targets or scan metadata publicly.
SafetyPermissions & scopesThe project documentation says the server uses outbound HTTPS only and blocks private/internal IP lookups, but users should still avoid unauthorized reconnaissance or sensitive internal target submission.
PrivacyLocal filesSecurity queries can reveal vulnerable products, internal triage priorities, asset names, IP addresses, domains, URLs, file hashes, package versions, malware interests, and investigation targets to upstream APIs.
PrivacyCredentials & tokensAPI keys are loaded from environment variables; keep them scoped, rotated, and out of model transcripts, shell history, and shared configuration files.
PrivacyData retentionThe implementation initializes a local SQLite cache and rotating audit log, which can retain query parameters, statuses, timings, source results, and security-investigation context.
PrivacyCredentials & tokensAudit logging redacts fields whose names include key or token, but other query values can still be sensitive and should be protected as security data.
PrivacyLocal filesThe repository license file is Apache-2.0 while the README badge and pyproject classifier currently mention MIT, so verify current licensing before redistribution or commercial reuse.
Safety notes
CVE, CVSS, EPSS, KEV, exploit, PoC, MITRE, package-advisory, malware, and IP-reputation data can be stale, incomplete, provider-specific, or false positive.
Treat generated risk scores and vulnerability reports as triage aids, not patch policy, incident-response authority, or compliance evidence by themselves.
Some tools can submit or query URLs, IP addresses, domains, file hashes, package names, repository search terms, and exploit indicators against third-party services.
Shodan, URLScan, VirusTotal, AbuseIPDB, GreyNoise, CIRCL, GitHub, VulnCheck, NVD, OSV, and other providers may apply rate limits, visibility rules, account terms, and retention policies.
Review provider defaults before scanning URLs or infrastructure because some services can expose submitted targets or scan metadata publicly.
The project documentation says the server uses outbound HTTPS only and blocks private/internal IP lookups, but users should still avoid unauthorized reconnaissance or sensitive internal target submission.
Privacy notes
Security queries can reveal vulnerable products, internal triage priorities, asset names, IP addresses, domains, URLs, file hashes, package versions, malware interests, and investigation targets to upstream APIs.
API keys are loaded from environment variables; keep them scoped, rotated, and out of model transcripts, shell history, and shared configuration files.
The implementation initializes a local SQLite cache and rotating audit log, which can retain query parameters, statuses, timings, source results, and security-investigation context.
Audit logging redacts fields whose names include key or token, but other query values can still be sensitive and should be protected as security data.
The repository license file is Apache-2.0 while the README badge and pyproject classifier currently mention MIT, so verify current licensing before redistribution or commercial reuse.
Prerequisites
Python 3.10 or newer for the source project, or a Python version supported by the currently published package.
pip, uv, or another supported Python package installer.
Network access to the selected vulnerability, threat-intelligence, and package-advisory APIs.
Optional API keys for NVD, GitHub, VulnCheck, AbuseIPDB, VirusTotal, URLScan, Shodan, GreyNoise, or CIRCL Passive DNS when those integrations are needed.
Authorization to query the CVEs, packages, domains, IP addresses, URLs, hashes, repositories, and security-investigation targets being analyzed.
CVE MCP Server is a Python Model Context Protocol server for security
intelligence and vulnerability triage. It exposes Claude to tools for CVE
lookup, NVD search, OSV dependency checks, EPSS scoring, CISA KEV checks, CVSS
parsing, vendor-advisory retrieval, exploit and PoC availability checks, MITRE
attack mapping, timeline generation, dependency scans, repository secret search,
IP reputation, passive DNS, Shodan host lookup, malware-family lookup, URL
safety checks, ransomware intelligence, risk scoring, and vulnerability reports.
The server runs over stdio with cve-mcp, uses outbound HTTPS for upstream data
sources, and supports optional API keys for higher-rate or provider-specific
integrations. Its implementation initializes a SQLite cache and rotating audit
log, validates selected inputs, and redacts audit fields whose names include
key or token.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, PyPI metadata, package metadata, implementation files, environment
template, security policy, and license file for current install commands, tool
behavior, optional credentials, audit/cache behavior, provider requirements, and
licensing.
Features
Python package and stdio MCP server launched with cve-mcp.
CVE lookup and search through NVD, with optional API key support for higher
request limits.
EPSS scoring, CISA KEV status checks, CVSS vector parsing, and vendor-advisory
lookup workflows.
OSV package vulnerability checks, dependency-list scans, container package
scans, and GitHub advisory or repository search workflows.
Exploit and PoC availability checks, MITRE attack mapping, CVE timeline
generation, risk scoring, CVE comparison, and vulnerability report generation.
Threat-intelligence workflows for IP reputation, passive DNS, Shodan host
data, file-hash intelligence, malware-family lookup, ransomware indicators,
and URL safety.
Optional provider credentials for NVD, GitHub, VulnCheck, AbuseIPDB,
VirusTotal, URLScan, Shodan, GreyNoise, and CIRCL Passive DNS.
SQLite cache and rotating audit log paths configurable through environment
variables.
Installation
Install the package, then configure your MCP client:
Restart the MCP client, then ask Claude to analyze an approved CVE, package,
domain, IP address, file hash, or URL. Add only the provider keys needed for the
specific tools you plan to use.
Use Cases
Triage a CVE by combining NVD details, EPSS probability, CISA KEV status,
exploit availability, and vendor advisory context.
Prioritize a backlog of vulnerabilities with transparent source evidence
before patch-window planning.
Check whether a package and version appears in OSV or GitHub advisory data.
Enrich an approved incident-response indicator with IP reputation, passive
DNS, malware, ransomware, URL, or file-hash intelligence.
Compare multiple CVEs and draft an evidence-backed vulnerability report for
human review.
Map vulnerability findings to MITRE attack context for security notes or
remediation discussions.
Safety and Privacy
Use CVE MCP Server as an intelligence retrieval and prioritization aid, not as a
replacement for vendor advisories, asset ownership checks, change-management
approval, or incident-response judgment. Security datasets differ by provider,
can change quickly, and can contain false positives or stale records.
Queries to third-party services can expose sensitive security context, including
assets, vulnerable packages, domains, IP addresses, file hashes, URLs, and
investigation focus. Review each provider's terms, visibility defaults, and
retention behavior before submitting sensitive targets. Protect the local cache,
rotating audit log, environment variables, MCP client configuration, and model
conversation history as security data.
The source repository's security notes say the server makes outbound HTTPS
requests only, does not open inbound ports, does not log API keys, and blocks
private/internal IP lookups. Those controls reduce risk, but they do not replace
authorization checks or provider-specific privacy review.
Duplicate Check
Existing MCP content includes security-adjacent entries such as ContrastAPI,
Socket, and HexStrike AI. CVE MCP Server is distinct because it covers
mukul975/cve-mcp-server, a Python stdio MCP server focused on CVE and
threat-intelligence lookup with optional provider keys, local SQLite cache,
rotating audit logs, and tools spanning CVE, EPSS, KEV, OSV, exploit signals,
MITRE mappings, IP/domain/hash/URL intelligence, risk scoring, and report
generation. No matching CVE MCP Server source URL or dedicated entry was found
in content/mcp.
Offensive-security MCP server from pentest-ai that lets Claude list and run wrapped security tools, plan and install missing tools, launch authorized engagements, run web, recon, API, cloud, AD, credential, vulnerability, mobile, wireless, and LLM-red-team assessments, and retrieve findings, attack chains, reports.
✓CVE, CVSS, EPSS, KEV, exploit, PoC, MITRE, package-advisory, malware, and IP-reputation data can be stale, incomplete, provider-specific, or false positive.
Treat generated risk scores and vulnerability reports as triage aids, not patch policy, incident-response authority, or compliance evidence by themselves.
Some tools can submit or query URLs, IP addresses, domains, file hashes, package names, repository search terms, and exploit indicators against third-party services.
Shodan, URLScan, VirusTotal, AbuseIPDB, GreyNoise, CIRCL, GitHub, VulnCheck, NVD, OSV, and other providers may apply rate limits, visibility rules, account terms, and retention policies.
Review provider defaults before scanning URLs or infrastructure because some services can expose submitted targets or scan metadata publicly.
The project documentation says the server uses outbound HTTPS only and blocks private/internal IP lookups, but users should still avoid unauthorized reconnaissance or sensitive internal target submission.
✓Treat CVE, EPSS, KEV, IOC, and OSINT enrichment as advisory input that still needs security review before acting on it.
✓Pentest AI is offensive security tooling that performs real network and host operations and can run wrapped scanners, fuzzers, password tools, exploit-adjacent probes, and custom HTTP requests.
Use only on targets where you have written permission, and keep rules of engagement, exclusions, rate limits, credentials, and scope boundaries in the prompt and engagement record.
Prefer intensity=safe, strict_scope=true, and respect_rate_limits=true for real targets; the upstream README notes these safety flags are not all default behavior.
Do not call ensure_tools_installed with auto_install=true until the exact tool list and install impact have been reviewed by a human.
Authenticated scans should use credential references or approved secret resolvers, not raw passwords, tokens, or session cookies pasted into model context.
External tools may create traffic, files, subprocesses, reports, findings databases, caches, and evidence artifacts that require cleanup and retention controls.
✓Searchcode analyzes public repositories through a hosted remote service; do not point it at private repository URLs unless you have a private/enterprise arrangement and have reviewed the current access controls.
The service can return code snippets, file contents, symbols, file trees, static-analysis findings, and credential-scan findings from public repositories.
Treat tool results as machine-assisted code intelligence. Confirm security findings, complexity claims, and dependency conclusions against the repository before making merge, hiring, acquisition, or incident decisions.
Large or repeated repository analysis can create automated traffic to Searchcode; keep agent loops bounded and avoid broad unattended scans.
Privacy notes
✓Security queries can reveal vulnerable products, internal triage priorities, asset names, IP addresses, domains, URLs, file hashes, package versions, malware interests, and investigation targets to upstream APIs.
API keys are loaded from environment variables; keep them scoped, rotated, and out of model transcripts, shell history, and shared configuration files.
The implementation initializes a local SQLite cache and rotating audit log, which can retain query parameters, statuses, timings, source results, and security-investigation context.
Audit logging redacts fields whose names include key or token, but other query values can still be sensitive and should be protected as security data.
The repository license file is Apache-2.0 while the README badge and pyproject classifier currently mention MIT, so verify current licensing before redistribution or commercial reuse.
✓Queried domains, IPs, dependencies, vulnerabilities, and indicators can reveal investigation targets and may enter model context.
✓Targets, URLs, IPs, domains, credentials references, findings, proofs of concept, screenshots, payloads, request/response data, reports, detection rules, process lists, and tool output can be sent to the MCP client and model.
Findings databases, generated reports, SARIF/JUnit/HTML/PDF exports, logs, subprocess output, tool caches, auth profiles, and cloud-sync settings can contain sensitive vulnerabilities and customer data.
Prompts and transcripts can disclose live vulnerabilities, exploitable paths, credentials handling, customer infrastructure, or engagement scope.
Keep cloud workspace sync, API tokens, LLM provider keys, and generated reports disabled or controlled unless the engagement explicitly allows them.
✓Prompts and tool inputs can reveal which public repositories, symbols, files, dependencies, security concerns, or candidate portfolios a team is investigating.
Returned code snippets, findings, file paths, and repository metadata become part of the MCP client transcript and may be processed by the connected model provider.
Public code can still contain secrets, personal data, proprietary code accidentally committed upstream, or prompt-injection text. Review returned snippets before forwarding them into other tools or reports.
Searchcode's public page says the hosted MCP server is free during beta and does not require signup or an API key; review the live site before production use because pricing and private-code options may change.
Prerequisites
Python 3.10 or newer for the source project, or a Python version supported by the currently published package.
pip, uv, or another supported Python package installer.
Network access to the selected vulnerability, threat-intelligence, and package-advisory APIs.
Optional API keys for NVD, GitHub, VulnCheck, AbuseIPDB, VirusTotal, URLScan, Shodan, GreyNoise, or CIRCL Passive DNS when those integrations are needed.
— none listed
Python 3.10 or newer and pip, uv, or another supported Python package installer.
Written authorization and explicit scope for every target, host, account, user, API, network, or application being tested.
A dedicated test environment or engagement workspace for findings, tool output, reports, and installed security tools.
Human approval before auto-installing external tools, running active probes, credential tests, authenticated scans, or exploit-chain validation.
MCP client with remote Streamable HTTP support, or `mcp-remote` for clients that still need a stdio bridge.
Public Git repository URLs or `owner/repo` names for the repositories Claude should inspect.
Team agreement that public repository metadata, code snippets, file paths, and static-analysis results may be sent through a hosted third-party MCP service.
Client-side policy for whether model-generated findings should be treated as triage hints or reviewed security results.
Install
pip install cve-mcp-server
claude mcp add --transport http contrastapi https://api.contrastcyber.com/mcp/
pip install ptai
claude mcp add searchcode --transport http https://api.searchcode.com/v1/mcp