Wass Mcp

io.github.tb0hdanPublished by GitHub account tb0hdanv1.0.4Updated Oct 24, 2026

MCP server for web application security scanning

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Runs web application security scans (Nikto, Nuclei, Wapiti, header checks) against a host and stores the results.

What you can do
WASS-MCP exposes tools that run four external security scanners against a target host and port: Nikto for web server issues, Nuclei for template-based vulnerability detection, Wapiti for web application flaws such as SQL injection and XSS, and shcheck.py for HTTP security header analysis. A full_scan tool runs all four in parallel and merges the output into one report. A history tool lists, retrieves, deletes, or clears stored scan results.
When to use it
Use it when you want an assistant to drive authorized security testing of web servers or applications you own or are permitted to test, and to keep a record of past scans. It is not a general browsing or monitoring tool.
Requirements
Runs as a local process, typically via Docker on 127.0.0.1:8989, or built from source with Go 1.25+ and SQLite3. The scanner binaries Nikto, Nuclei, Wapiti, and shcheck must be installed for the corresponding tools to work. No accounts, API keys, or environment variables are declared.
Before you install
The scanners send active attack traffic to whatever host is given, so only scan systems you are authorized to test; unauthorized scanning may be illegal. The history tool can delete individual records or clear all stored scan history. The README also mentions debug profiling endpoints, which should not be exposed beyond localhost.

Installation

In SourceWeft

  1. Open Wass Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

WASS-MCP

A Model Context Protocol (MCP) server for web application security scanning.

Features

  • MCP Protocol Support - Full compatibility with MCP clients (Claude, etc.)
  • Nikto Integration - Web server vulnerability scanning
  • Nuclei Integration - Template-based vulnerability scanning
  • Wapiti Integration - Web application vulnerability scanning
  • Shcheck Integration - Security headers analysis
  • Execution History - Persistent storage of scan results
  • Stateless Design - Survives server restarts without session errors
  • RESTful HTTP Transport - Streamable HTTP-based MCP protocol

Usage

bash
docker run -p 127.0.0.1:8989:8989 tb0hdan/wass-mcp

MCP Client Configuration

Example command to add WASS-MCP server to Claude MCP clients:

bash
claude mcp add wass-mcp --transport http http://127.0.0.1:8989

or Gemini:

bash
gemini mcp add wass-mcp --transport http http://127.0.0.1:8989

Available Tools

nikto

Perform web server vulnerability scans using Nikto.

Parameters:

NameTypeRequiredDescription
hoststringYesTarget hostname or IP address
portintegerNoTarget port (default: 80)
vhoststringNoVirtual host header
max_linesintegerNoMaximum output lines
offsetintegerNoOutput line offset

Example:

json
{  "host": "192.168.1.100",  "port": 443}

nuclei

Perform template-based vulnerability scanning using Nuclei.

Parameters:

NameTypeRequiredDescription
hoststringYesTarget hostname or IP address
portintegerNoTarget port (default: 80)
vhoststringNoVirtual host header
max_linesintegerNoMaximum output lines
offsetintegerNoOutput line offset

Vulnerabilities Detected:

  • CVE detection via community templates
  • Misconfigurations
  • Exposed panels/dashboards
  • Default credentials
  • Technology detection
  • Security headers analysis
  • And many more via 8000+ community templates

Example:

json
{  "host": "192.168.1.100",  "port": 443}

wapiti

Perform comprehensive web application vulnerability scans using Wapiti.

Parameters:

NameTypeRequiredDescription
hoststringYesTarget hostname or IP address
portintegerNoTarget port (default: 80)
vhoststringNoVirtual host header
max_linesintegerNoMaximum output lines
offsetintegerNoOutput line offset

Vulnerabilities Detected:

  • SQL Injection / Blind SQL Injection
  • Cross-Site Scripting (XSS)
  • File Inclusion / Path Traversal
  • Command Execution
  • CRLF Injection
  • Server-Side Request Forgery (SSRF)
  • Open Redirects
  • HTTP Security Headers
  • Content Security Policy issues

Example:

json
{  "host": "192.168.1.100",  "port": 8080}

shcheck_py

Analyze HTTP security headers using shcheck.py.

Parameters:

NameTypeRequiredDescription
hoststringYesTarget hostname or IP address
portintegerNoTarget port (default: 80)
vhoststringNoVirtual host header
max_linesintegerNoMaximum output lines
offsetintegerNoOutput line offset

Headers Analyzed:

  • Content-Security-Policy
  • Strict-Transport-Security
  • X-Frame-Options
  • X-Content-Type-Options
  • Referrer-Policy
  • Permissions-Policy
  • And other security-relevant headers

Example:

json
{  "host": "example.com",  "port": 443}

full_scan

Perform a comprehensive security scan using all available scanners in parallel.

Parameters:

NameTypeRequiredDescription
hoststringYesTarget hostname or IP address
portintegerNoTarget port (default: 80)
vhoststringNoVirtual host header
max_linesintegerNoMaximum output lines
offsetintegerNoOutput line offset

Features:

  • Runs nikto, nuclei, wapiti and shcheck scanners in parallel
  • Merges results into a unified report
  • Includes timing and status for each scanner
  • Gracefully handles missing scanner binaries

Example:

json
{  "host": "192.168.1.100",  "port": 8080}

history

Browse and manage tool execution history.

Parameters:

NameTypeRequiredDescription
actionstringYesOne of: list, get, delete, clear
idintegerFor get/deleteExecution ID
limitintegerNoResults per page (default: 10)
offsetintegerNoPagination offset

Actions:

  • list - List execution history with pagination
  • get - Get full details of a specific execution
  • delete - Delete a specific execution by ID
  • clear - Delete all execution history

API Endpoints

EndpointDescription
POST /mcpMCP protocol endpoint
GET /Service information (JSON)
GET /debug/pprof/*Profiling endpoints

Development and advanced usage

Source build requirements

  • Go 1.25+
  • Nikto (apt install nikto or equivalent)
  • Nuclei (go install github.com/projectdiscovery/nuclei/v3/cmd/nuclei@latest)
  • Wapiti (apt install wapiti or equivalent)
  • Shcheck (pip install shcheck or from GitHub)
  • SQLite3
bash
# Clone the repositorygit clone https://github.com/tb0hdan/wass-mcp.gitcd wass-mcp
# Buildmake build
# Run./build/wass-mcp

Starting the Server

bash
# Default (localhost:8989)./build/wass-mcp
# Custom bind address./build/wass-mcp --bind 0.0.0.0:8080
# Custom database path./build/wass-mcp --db /var/lib/wass-mcp/data.db
# Debug mode./build/wass-mcp --debug

Configuration Options

FlagDefaultDescription
--bindlocalhost:8989HTTP server bind address
--db./wass-mcp.dbSQLite database file path
--debugfalseEnable debug logging
--version-Print version and exit

Linting

bash
make lint

Testing

bash
make test

Project Structure

wass-mcp/├── cmd/wass-mcp/        # Application entry point├── pkg/│   ├── server/          # MCP server wrapper│   ├── storage/         # Database layer (SQLite/GORM)│   ├── models/          # Data models│   ├── tools/           # MCP tool implementations│   │   ├── nikto/       # Nikto web server scanner│   │   ├── wapiti/      # Wapiti web app scanner│   │   ├── nuclei/      # Nuclei template scanner│   │   ├── shcheck/     # Security headers checker│   │   ├── fullscan/    # Parallel full scan│   │   └── history/     # History management│   └── types/           # Shared types and constants├── docs/                # Documentation└── build/               # Build output and coverage reports

Security Notice

This tool is intended for authorized security testing only. Ensure you have proper authorization before scanning any systems. Unauthorized scanning may be illegal in your jurisdiction.

Project notes

For complete project notes, design decisions, and architecture overview, please refer to the Project Notes document.

License

BSD 3-Clause License - Copyright (c) 2026, Bohdan Turkynevych. See LICENSE for details.

Contributing

  1. Fork the repository
  2. Create a feature branch (git checkout -b feature/new-tool)
  3. Commit your changes (git commit -am 'Add new scanning tool')
  4. Push to the branch (git push origin feature/new-tool)
  5. Create a Pull Request

Acknowledgments

Source: README.md at commit 925bf72

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.4LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts