Tenable Security MCP
Related Servers
Alternatives to Tenable Security MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude Desktop to run real vulnerability scans using Nuclei through natural language commands.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents like Claude Desktop to read vulnerability reports, trigger scans, and manage findings for the Inventory Guard self-hosted vulnerability watchdog.-
- AlicenseNot gradedqualityDmaintenanceEnables natural language interaction with Tenable Nessus for vulnerability scans, policy management, and report generation.1MIT
- AlicenseNot gradedqualityCmaintenanceIntegrates 15+ static application security testing tools (Semgrep, Bandit, TruffleHog, etc.) with Claude Code AI, enabling automated vulnerability scanning and security analysis through natural language commands. Supports cross-platform operation with remote execution on dedicated security VMs.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered security scanning of codebases through conversational analysis, allowing users to assess, threat model, code review, DAST test, and generate security reports using natural language with Claude.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI-assisted SOC workflows by connecting Claude Desktop to Splunk Enterprise for security event analysis and incident response.-
TDQS
Scored across 32 tools
Most tools target distinct resources or actions, but CVE-intelligence tools overlap heavily: search_security_intelligence, get_complete_cve_intelligence, and the component tools (get_cve_intelligence, get_cisa_kev_status, get_epss_score, get_exploit_intelligence) can be confused. prioritize_vulnerabilities and analyze_emerging_threats also use similar signals for related outputs, though descriptions help separate them.
Tool names consistently use snake_case with predictable verb_noun or verb_resource patterns. Prefixes such as list_, get_, launch_, stop_, and search_ are used throughout, with no mixed camelCase or chaotic naming.
The server exposes 32 tools, which is above the 25+ threshold for being too many and includes several overlapping intelligence and scan-detail operations that could be consolidated. While the domain is broad, the tool count feels excessive rather than tightly scoped.
The surface covers Nessus scan listing, launching, stopping, history, host/vulnerability details, Tenable cloud assets and vulnerabilities, and major CVE intelligence sources. Gaps exist for creating, updating, or deleting scans, policies, users, and reports, but core analysis and scan-control workflows are present.