Labsco
MCP SERVER

Nessus MCP Server

by Cyreslab-AI

Start Nessus scans, watch them run and read the findings back, and rehearse the whole flow before touching a real scanner.

Vulnerability Scanning & Application Security
Summary
Drive a scan from the conversation where you are already triaging.

Start, poll, read results is the loop that normally means tabbing into the Nessus console and back. Mock mode is the detail worth knowing about: you can wire the tools into an agent, see the shapes they return and fix the prompt, all before pointing anything at a live scanner.

What it is

A bridge to the Tenable Nessus vulnerability scanner. It starts scans against targets, tracks them, returns results and looks up vulnerability detail. By default it runs in a mock mode, so the tool surface works before a Nessus instance is wired up.

What you get
  • The scan templates your Nessus offers (list_scan_templates)
  • A new scan started against a target (start_scan), its status while it runs (get_scan_status) and its results once it finishes (get_scan_results)
  • Every scan and where it stands (list_scans)
  • Detailed information about a specific vulnerability (get_vulnerability_details)
  • Keyword search across vulnerabilities (search_vulnerabilities)
  • A fully functional mock mode that needs no Nessus API key
Requirements

Node.js 16 or higher and a local build with npm install and npm run build. To reach a real scanner, put the scanner's address and its access key and secret key in the environment; leave them unset and the server stays in mock mode.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary