A
licenseA
qualityF
maintenanceDependency security & health auditing for AI agents with no account or API key required.
2
2
MIT
Security Intel MCP
by datakoot
Related Servers
Alternatives to Security Intel MCP
No user-submitted related servers found.
Related Servers
Fetter MCPofficial
FlicenseNot gradedqualityDmaintenanceProvides real-time Python package vulnerability data, enabling AI agents to check CVEs, CVSS scores, and safe versions for informed dependency decisions.1-- AlicenseAqualityAmaintenanceDependency intelligence for AI agents. CVE scanning, health checks, upgrade planning.9394 npm2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides security checks for AI agents, including secret scanning, CVE lookup, and dependency vulnerability scanning, all running locally except for CVE lookups.MIT
- 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
- AlicenseNot gradedqualityDmaintenanceProvides multi-source vulnerability intelligence for AI-powered security operations, combining NVD CVSS, CISA KEV, and EPSS scores without requiring an API key.1MIT
TDQS
A3.8/5.0
Scored across 5 tools
Disambiguation4/5
The five tools mostly target distinct resources: individual CVE lookup, KEV catalog queries, EPSS scoring, per-package OSV lookup, and manifest-wide auditing. However, cve_lookup already bundles KEV and EPSS results inline, so an agent may be unsure when to call the dedicated known_exploited or epss_score tools versus the composite lookup. The package_vulnerabilities vs audit_dependencies split is clear (single package vs whole manifest).
Naming Consistency3/5
Names are readable but follow mixed conventions: cve_lookup, known_exploited, epss_score, package_vulnerabilities, and audit_dependencies blend noun_noun, adjective-style, and verb_noun forms. Two tools (audit_dependencies, package_vulnerabilities) use verb-based action naming while others are noun phrases. Not chaotic, but no single predictable pattern.
Tool Count5/5
Five tools is a tight, well-scoped surface for a security-intelligence server covering CVE data, exploit likelihood, and dependency auditing. Each tool earns its place without redundancy or thinness. No unused or filler tools.
Completeness4/5
The surface covers the core workflows: CVE detail, known-exploited status, EPSS prioritization, package lookup, and full manifest auditing. Minor gaps exist, such as keyword/vendor-based CVE search or advisory text search, but agents can work around these via CVE IDs and OSV queries.
Maintenance
ActivityActive
ResponsivenessNo issues