Aegis MCP
Related Servers
Alternatives to Aegis MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceUnifies NVD, EPSS, CISA KEV, GitHub Advisory, and OSV into a single MCP server, enabling AI agents to query vulnerability intelligence conversationally with 23 tools for incident response, prioritization, dependency audits, and threat monitoring.41292 npm30MIT
- AlicenseAqualityAmaintenanceEnables any MCP client (Claude Code, Claude Desktop, Codex, or a custom agent) to fetch the latest CVEs at query time from live sources — NVD, CVE List V5, GitHub Advisory Database, CISA KEV and FIRST EPSS — without a separate API key. Exposes search, filtering (severity, RCE, PoC, KEV, keyword, CPE), per-CVE detail and risk-scored patch prioritization as JSON tools, so answers are grounded in live data rather than model memory.61MIT
- AlicenseAqualityBmaintenanceEnables AI agents to search, correlate, and monitor real-time vulnerability intelligence from NVD, CISA KEV, EPSS, and MITRE ATT&CK, including CVE details, critical CVE tracking, known exploited vulnerabilities, and exploitation probability scores.52MIT
- AlicenseNot gradedqualityDmaintenanceProvides CVE lookup, search, and exploit intelligence from public vulnerability sources (NVD, CISA KEV, EPSS) for AI agents to produce remediation guidance without consuming LLM tokens for data fetching.1MIT
- AlicenseAqualityBmaintenanceEnables LLMs to access realtime CVE intelligence aggregated from NVD, CISA KEV, EPSS, GitHub advisories, PoC discovery, and Metasploit/Nuclei tooling, providing vulnerability details, exploitation signals, and prioritized triage verdicts.1221 npm3MIT
- AlicenseAqualityBmaintenanceVulnerability intelligence for AI agents that enables CVE lookup, package vulnerability checks, and dependency auditing without API keys.5MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct role: known-CVE enrichment, keyword discovery, package/version scanning, incident triage workflow, report retrieval, and server health. The boundaries between lookup_cve, search_vulnerabilities, scan_packages, and triage_incident are explicitly described and unlikely to cause misselection.
Most tool names follow a clear verb_noun pattern such as lookup_cve, triage_incident, search_vulnerabilities, scan_packages, and get_incident_report. server_health is a minor deviation because it lacks a verb, but the overall convention is still predictable.
Six tools is well-scoped for a vulnerability intelligence and incident triage server. Each tool covers a meaningful part of the workflow without obvious redundancy.
The surface covers the core lifecycle: CVE lookup, vulnerability discovery, package scanning, incident triage, persisted report retrieval, and health checks. Minor gaps exist around listing or browsing prior incident reports and broader asset inventory, but agents can work around these.