cve-mcp-server
Production-grade MCP server providing Claude access to multiple cybersecurity tools and APIs
GraphCanon updated 4w · GitHub synced 4w
Decision brief
cve-mcp-server offers production-grade integration of Claude with diverse cybersecurity APIs and tools.
Good fit when
- Use cve-mcp-server when you need to provide comprehensive threat intelligence and vulnerability management capabilities to the LLM 'Claude', leveraging 27 security intelligence tools.
- Consider it if your project specifically requires seamless interaction between Claude and a range of cybersecurity APIs, including but not limited to CVE lookup, EPSS scoring, and CISA KEV.
Avoid when
- Avoid cve-mcp-server if your application does not require integration with the specific set of cybersecurity tools it provides or if a different LLM is preferred.
- Do not use this tool if you need to integrate only one or two security APIs; its strength lies in its extensive library of integrations, which might be overkill for smaller scale projects.
- Hosting:
- self hosted - This tool needs to be hosted and run on your own infrastructure.
- Requirements:
- cve-mcp-server requires a Python environment.; Proper API keys for accessing various security tools and APIs are necessary.
Observed Jul 16, 2026 · Source: enrich:decision_facts
Verify the decision
Maintenance and security
Full trust report- Maintenance
- Active (10d since push)
- As of 4w
- Provenance
- Not a fork · Personal account
- As of 4w
- Security (OSV)
- No MCP manifest
- As of 1mo
Public GitHub metadata and optional OSV scans. Signals, not a guarantee. Trust methodology.
Install
pip install cve-mcp-serverSimilar tools
Same-category neighbours. No typed graph edges are catalogued for this tool yet.
Evidence and technical details
Sourced facts, taxonomy, compatibility claims, README excerpt, and machine-readable endpoints.
Overview
This repository hosts a production-ready server that integrates a variety of security intelligence APIs, allowing the LLM 'Claude' to interact with them for improved threat intelligence and vulnerability management.
Capability facts
- Deploy
- Self-host
Source: dockerfile:Dockerfile · Jul 27, 2026
- Docker
- Dockerfile present
Source: dockerfile:Dockerfile · Jul 27, 2026
- CLI
- CLI entrypoint
Source: pyproject.toml:[project.scripts] · Jul 27, 2026
- Languages
- python
Source: github.language+pyproject.toml · Jul 27, 2026
Categories
Compatibility
Sourced claims from the README excerpt - not unsourced marketing copy.
Source: README excerpt (regex_v1, Jul 27, 2026)
python -m venv venv && source venv/bin/activateSource link
Tags
README
3. Install dependencies
pip install -e .
Step 1: Install (2 minutes)
git clone https://github.com/mukul975/cve-mcp-server.git
cd cve-mcp-server
python -m venv venv && source venv/bin/activate
pip install -e .
Scenario 2: "Scan my Python requirements.txt"
You: Scan these dependencies: requests==2.28.0, flask==2.2.0, django==3.2.0, pillow==9.0.0, cryptography==37.0.0
→ scan_dependencies(ecosystem="PyPI", packages={...})
Found 12 vulnerabilities across 4 packages
Claude's response: "Found 12 vulnerabilities across your packages. Immediate action: Django 3.2.0 (3 critical CVEs including SQL injection), Pillow 9.0.0 (heap overflow), cryptography 37.0.0 (OpenSSL chain). Upgrade to: django>=4.2.16, pillow>=10.3.0, cryptography>=42.0.0."
Testing requirements
- All new tools must have at least one offline test with mocked responses
- Risk score changes must include formula verification test cases
- Network tools must include a test verifying private IP blocking
- All tests must pass:
pytest tests/ -v
📄 License
MIT License — see LICENSE for details.
Copyright (c) 2025-2026 Mahipal Jangra (mukul975)
Built with 🔐 by Mahipal Jangra · Berlin, Germany
Turning security intelligence into conversation.
For agents
This page has a .md twin and JSON over the API.