Skip to main content
Glama
Tenable Security MCP

Tenable Security MCP

πŸ” Tenable Security MCP

AI-Assisted Vulnerability Management with Claude Desktop


Related MCP server: Nessus MCP Server

πŸ“‹ Executive Summary

Tenable Security MCP is a cutting-edge Model Context Protocol (MCP) server that unifies vulnerability management intelligence, enabling security teams to leverage AI for rapid threat prioritization and remediation planning.

🎯 Transform this:

Nessus β†’ CVE β†’ CVSS β†’ EPSS β†’ CISA KEV β†’ Exploit Research β†’ Risk Assessment

✨ Into this:

Claude Desktop β†’ Tenable Security MCP β†’ Unified Intelligence β†’ Actionable Insights

🎯 Core Capabilities

πŸ” Nessus Operations

  • βœ… Retrieve server information and scan details

  • βœ… List, launch, and manage scans

  • βœ… Access granular host and vulnerability data

  • βœ… Manage policies, folders, and agent deployments

πŸ›‘οΈ Vulnerability Intelligence

  • βœ… Enrich findings with CVE details (NVD)

  • βœ… Cross-reference CVSS scores & EPSS probabilities

  • βœ… Check CISA Known Exploited Vulnerabilities (KEV)

  • βœ… Aggregate public exploit and PoC intelligence

πŸ“Š Risk Prioritization Engine

Intelligent correlation across multiple signals:

  • πŸ”΄ Nessus severity ratings

  • πŸ“ˆ CVSS base & temporal scores

  • ⚑ EPSS exploitation probability

  • 🚨 CISA KEV status

  • πŸ’£ Public exploit availability

  • 🏒 Asset context & criticality

πŸ’¬ Example Queries

"Analyze my latest scan and list critical findings"
"Get complete intelligence for CVE-2024-3094"
"Which vulnerabilities require urgent remediation?"
"Prioritize findings using severity, CVSS, EPSS, and exploit data"
"Create a remediation roadmap for high-risk assets"

πŸ—οΈ Architecture Overview

πŸ”— Integration Model

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚         Claude Desktop Application              β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                   β”‚
                   β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚   Tenable Security MCP Server (Python)          β”‚
└──┬─────────────┬──────────────┬────────────────┐
   β”‚             β”‚              β”‚                β”‚
   β–Ό             β–Ό              β–Ό                β–Ό
Nessus      NVD/CVE        EPSS/CISA        Exploit
(Local)     (Public)       (Public)         Intelligence

πŸ”’ Security Design

  • 🟒 Nessus stays local - No public internet exposure required

  • 🟒 MCP handles external APIs - Isolated API credential management

  • 🟒 Zero trust - All data validated and contextualized

  • 🟒 Analyst-in-the-loop - AI assists, humans decide


πŸš€ Quick Start

πŸ“¦ Prerequisites

  • βœ… Claude Desktop (latest version)

  • βœ… Nessus Essentials or Professional/Expert

  • βœ… Nessus API keys (access key + secret key)

  • βœ… Git installed


πŸ”§ Installation Guide

Step 1️⃣: Clone Repository

git clone https://github.com/kasireddy-sec/tenable-security-mcp.git
cd tenable-security-mcp

Step 2️⃣: Build Extension

  1. Push changes to GitHub (or trigger manually)

  2. Navigate to: Actions β†’ build.yml

  3. Click Run workflow

  4. Wait for completion (2-3 minutes)

  5. Download extension.mcpb artifact

Option B: Local Build

# Install MCP build tools
pip install -r requirements.txt

# Build the extension
mcp build

# Verify output
ls dist/extension.mcpb

Step 3️⃣: Install to Claude Desktop

  1. Open Claude Desktop

  2. Navigate to: Settings β†’ Extensions β†’ Advanced Settings

  3. Click Install Extension

  4. Select extension.mcpb file

  5. Enable the extension

Step 4️⃣: Configure Nessus

  1. Go to: Settings β†’ Extensions β†’ Tenable Security MCP

  2. Click Configure and enter:

    • Nessus URL: https://localhost:8834

    • API Access Key: your_access_key_here

    • API Secret Key: your_secret_key_here

Step 5️⃣: Verify Installation

# In Claude Desktop, test with:
"Get my Nessus server information"

βœ… You should receive live Nessus data!


πŸ“Š Practical Security Workflows

πŸ”΄ Critical Incident Response

"Analyze my latest scan and list critical findings with affected hosts"

β†’ Immediate visibility into high-risk assets

πŸ” CVE Deep Dive

"Get complete intelligence for CVE-2024-3094: CVSS, EPSS, CISA KEV, and exploit status"

β†’ Comprehensive threat context in seconds

πŸ“ˆ Smart Prioritization

"Which 5 vulnerabilities pose highest risk based on EPSS, exploitability, and asset criticality?"

β†’ Data-driven remediation sequencing

πŸ—“οΈ Coverage Assessment

"Identify assets that haven't been scanned in the last 7 days"

β†’ Risk visibility across your estate

πŸ› οΈ Remediation Planning

"Create a prioritized roadmap for findings above CVSS 7.0 with CISA KEV or public exploits"

β†’ Structured remediation strategy


🏒 Technology Stack

Component

Technology

Language

Python 3.9+

Framework

MCP Python SDK

Transport

HTTPS/REST

APIs

Nessus, NVD, EPSS, CISA KEV, Exploit Intelligence

Build Tool

GitHub Actions + MCP Build


πŸ“ Project Structure

tenable-security-mcp/
β”œβ”€β”€ πŸ“‚ .github/workflows/
β”‚   β”œβ”€β”€ test.yml              # Automated testing pipeline
β”‚   └── build.yml             # MCPB packaging & release
β”œβ”€β”€ πŸ“‚ extension/
β”‚   β”œβ”€β”€ manifest.json         # Extension metadata
β”‚   β”œβ”€β”€ pyproject.toml        # Dependencies & configuration
β”‚   └── πŸ“‚ src/
β”‚       └── server.py         # MCP server implementation
β”œβ”€β”€ pyproject.toml            # Project configuration
└── README.md                 # This file

πŸ”„ Build & Release Pipeline

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚       Developer Pushes to GitHub                β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                     β”‚
                     β–Ό
        β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
        β”‚  GitHub Actions Triggered  β”‚
        β””β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”˜
             β”‚                   β”‚
             β–Ό                   β–Ό
        β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”      β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
        β”‚Run Tests β”‚      β”‚ Build MCPB   β”‚
        β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜      β””β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜
                                 β”‚
                     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                     β”‚ extension.mcpb Created β”‚
                     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                 β”‚
                     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                     β”‚ Download from Workflow    β”‚
                     β”‚ Install to Claude        β”‚
                     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

⚠️ Known Issues & Solutions

πŸͺŸ Windows MSIX Installation Issue

Problem:

can't open file ... src/server.py
[Errno 2] No such file or directory

Root Cause: MSIX resolves MCP server paths incorrectly

Solution: Use standard Claude Desktop installer (not MSIX/enterprise)

βœ… Recommended: Standard installer for Windows users

🐍 UV / Python Permission Denied

Problem:

Access is denied (installing dependencies)

Root Cause: Microsoft Store Python has restricted write permissions

Solution: Extension uses isolated user-level UV environment

βœ… No manual action needed - automatic fallback enabled


πŸ”’ Security Best Practices

βœ… DO

  • 🟒 Store Nessus API credentials in configuration (never commit to repo)

  • 🟒 Use standard Claude Desktop installer

  • 🟒 Validate Claude's recommendations before production changes

  • 🟒 Treat exploit intelligence as supporting evidence

  • 🟒 Maintain audit logs of all vulnerability assessments

❌ DON'T

  • πŸ”΄ Commit API credentials to GitHub

  • πŸ”΄ Expose local Nessus to public internet

  • πŸ”΄ Scan systems without proper authorization

  • πŸ”΄ Treat AI recommendations as definitive without analyst review

  • πŸ”΄ Share sensitive finding details in untrusted environments


🀝 Contributing

We welcome contributions from the security community!

Development Workflow

# 1. Fork repository
git clone https://github.com/YOUR-USERNAME/tenable-security-mcp.git

# 2. Create feature branch
git checkout -b feature/your-feature-name

# 3. Make changes to extension/src/server.py
# ... your code changes ...

# 4. Test locally
mcp build
mcp run

# 5. Commit and push
git add .
git commit -m "Add: your feature description"
git push origin feature/your-feature-name

# 6. Submit Pull Request
# GitHub Actions will automatically build and test

Contribution Guidelines:

  • πŸ“‹ Follow Python PEP 8 style guide

  • πŸ§ͺ Include test cases for new features

  • πŸ“ Update documentation

  • βœ… Ensure GitHub Actions passes all checks


πŸ“„ License

MIT License - Open source and free to use

See LICENSE file for complete details


🎯 Vision

Transform vulnerability management from reactive firefighting to strategic risk management.

  • πŸ” Faster Analysis - Minutes instead of hours

  • πŸ’‘ Better Decisions - AI-assisted prioritization

  • πŸ“‰ Reduced Risk - Intelligent remediation

  • ⏱️ Increased Velocity - Automate the routine


πŸ“ž Support & Resources

Resource

Link

GitHub Issues

Report Bug / Request Feature

Documentation

README.md (you are here)

Tenable Docs

Nessus API Reference

CISA KEV

Known Exploited Vulnerabilities

EPSS

Exploit Prediction Scoring System


πŸš€ Built to Turn Raw Nessus Findings into Actionable Security Intelligence

Tenable Security MCP β†’ Faster Analysis β†’ Better Decisions β†’ Reduced Risk

License: MIT Python 3.9+

Made for Security Professionals | Built on MCP | Powered by Claude AI

Available Tools

32 tools
analyze_emerging_threatsB

Identify high-priority emerging vulnerability signals in a Nessus scan.

Signals include:

  • CISA KEV

  • high EPSS

  • public exploit evidence

  • high CVSS

  • critical/high Nessus severity

This does NOT claim that an unknown zero-day has been discovered. It identifies vulnerabilities requiring urgent investigation.

Inputs: scan_id (required), max_items. Returns: result

build_security_contextC

Build a normalized security-intelligence record suitable for downstream RAG or LLM reasoning.

Inputs: cve_id (required). Returns: result

find_assets_not_scanned_sinceA

Find Nessus hosts whose latest known scan result is older than the specified number of days.

Example: find_assets_not_scanned_since(7)

Inputs: days. Returns: result

get_cisa_kev_statusA

Check whether a CVE is listed in the CISA Known Exploited Vulnerabilities catalog.

Inputs: cve_id (required). Returns: result

get_complete_cve_intelligenceB

Combine NVD, CISA KEV, EPSS and public exploit intelligence for one CVE.

Inputs: cve_id (required). Returns: result

get_cve_intelligenceC

Retrieve detailed vulnerability intelligence from NVD.

Includes:

  • description

  • CVSS v4

  • CVSS v3.1

  • CVSS v3.0

  • CWE

  • affected configurations

  • references

  • publication date

  • modification date

Inputs: cve_id (required). Returns: result

get_epss_scoreC

Get the current FIRST EPSS score and percentile for a CVE.

Inputs: cve_id (required). Returns: result

get_exploit_intelligenceB

Search public GitHub repository metadata for exploit, PoC, scanner and proof-of-concept references related to a CVE.

This is intelligence evidence, not proof that an exploit works against a specific target.

Inputs: cve_id (required). Returns: result

get_mcp_capabilitiesB

Show the capabilities available through the Tenable Security MCP server.

Inputs: no named parameters. Returns: result

get_nessus_host_detailsC

Get vulnerability information for a host in a scan.

Inputs: host_id (required), scan_id (required). Returns: result

get_nessus_pluginC

Get information about a Nessus plugin.

Inputs: plugin_id (required). Returns: result

get_nessus_scan_detailsC

Get details and latest results for a Nessus scan.

Inputs: scan_id (required). Returns: result

get_nessus_scan_historyC

Get historical runs of a Nessus scan.

Inputs: scan_id (required). Returns: result

get_nessus_scan_history_detailsC

Get details for a specific historical scan result.

Inputs: scan_id (required), history_id (required). Returns: result

get_nessus_scan_statusC

Get the current status of a Nessus scan.

Inputs: scan_id (required). Returns: result

get_nessus_server_infoB

Get basic information about the Nessus server.

Inputs: no named parameters. Returns: result

get_nessus_vulnerability_detailsC

Get detailed information and plugin output for a vulnerability.

Inputs: host_id (required), scan_id (required), plugin_id (required). Returns: result

get_tenable_cloud_assetC

Get details for a Tenable Vulnerability Management asset.

Inputs: asset_uuid (required). Returns: result

get_tenable_cloud_server_infoC

Get information from the configured Tenable cloud environment.

Requires TENABLE_CLOUD_ACCESS_KEY and TENABLE_CLOUD_SECRET_KEY.

Inputs: no named parameters. Returns: result

get_tenable_cloud_vulnerabilityC

Get vulnerability information from Tenable Vulnerability Management.

Inputs: plugin_id (required). Returns: result

launch_nessus_scanC

Launch a Nessus scan using its configured targets.

Inputs: scan_id (required). Returns: result

list_nessus_agentsC

List Nessus agents.

Inputs: no named parameters. Returns: result

list_nessus_foldersB

List Nessus scan folders.

Inputs: no named parameters. Returns: result

list_nessus_policiesB

List available Nessus scan policies.

Inputs: no named parameters. Returns: result

list_nessus_scansB

List all scans configured in Nessus.

Inputs: no named parameters. Returns: result

list_nessus_usersB

List users configured in Nessus.

Inputs: no named parameters. Returns: result

list_nessus_vulnerabilitiesA

List vulnerabilities discovered in a Nessus scan.

Optional filters:

  • severity: info, low, medium, high, critical

  • cve: CVE identifier

  • host: hostname/IP fragment

Inputs: scan_id (required), cve, host, severity. Returns: result

list_tenable_cloud_assetsC

List assets from Tenable Vulnerability Management.

Inputs: limit. Returns: result

list_tenable_cloud_vulnerabilitiesC

List vulnerabilities from Tenable Vulnerability Management.

Inputs: limit. Returns: result

prioritize_vulnerabilitiesB

Prioritize vulnerabilities from a Nessus scan using:

  • Nessus severity

  • CVSS

  • EPSS

  • CISA KEV exploitation status

  • public exploit evidence

The score is a deterministic prioritization score and should not be interpreted as an official vendor score.

Inputs: scan_id (required), max_items. Returns: result

search_security_intelligenceC

Unified security intelligence lookup.

Searches:

  • NVD

  • CISA KEV

  • EPSS

  • public exploit intelligence

  • normalized security context

Inputs: cve_id (required). Returns: result

stop_nessus_scanC

Stop a running Nessus scan.

Inputs: scan_id (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.8/5.0

    Scored across 32 tools

    Disambiguation3/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Integrates 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.
      7
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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