wass-mcp
MCP server for web application security scanning with Nikto, Nuclei, Wapiti, and shcheck integration.
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
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:
claude mcp add wass-mcp --transport http http://127.0.0.1:8989
or Gemini:
gemini mcp add wass-mcp --transport http http://127.0.0.1:8989
Available Tools
nikto
Perform web server vulnerability scans using Nikto.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
host |
string | Yes | Target hostname or IP address |
port |
integer | No | Target port (default: 80) |
vhost |
string | No | Virtual host header |
max_lines |
integer | No | Maximum output lines |
offset |
integer | No | Output line offset |
Example:
{
"host": "192.168.1.100",
"port": 443
}
nuclei
Perform template-based vulnerability scanning using Nuclei.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
host |
string | Yes | Target hostname or IP address |
port |
integer | No | Target port (default: 80) |
vhost |
string | No | Virtual host header |
max_lines |
integer | No | Maximum output lines |
offset |
integer | No | Output 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:
{
"host": "192.168.1.100",
"port": 443
}
wapiti
Perform comprehensive web application vulnerability scans using Wapiti.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
host |
string | Yes | Target hostname or IP address |
port |
integer | No | Target port (default: 80) |
vhost |
string | No | Virtual host header |
max_lines |
integer | No | Maximum output lines |
offset |
integer | No | Output 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:
{
"host": "192.168.1.100",
"port": 8080
}
shcheck_py
Analyze HTTP security headers using shcheck.py.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
host |
string | Yes | Target hostname or IP address |
port |
integer | No | Target port (default: 80) |
vhost |
string | No | Virtual host header |
max_lines |
integer | No | Maximum output lines |
offset |
integer | No | Output 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:
{
"host": "example.com",
"port": 443
}
full_scan
Perform a comprehensive security scan using all available scanners in parallel.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
host |
string | Yes | Target hostname or IP address |
port |
integer | No | Target port (default: 80) |
vhost |
string | No | Virtual host header |
max_lines |
integer | No | Maximum output lines |
offset |
integer | No | Output 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:
{
"host": "192.168.1.100",
"port": 8080
}
history
Browse and manage tool execution history.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
action |
string | Yes | One of: list, get, delete, clear |
id |
integer | For get/delete | Execution ID |
limit |
integer | No | Results per page (default: 10) |
offset |
integer | No | Pagination offset |
Actions:
list- List execution history with paginationget- Get full details of a specific executiondelete- Delete a specific execution by IDclear- Delete all execution history
API Endpoints
| Endpoint | Description |
|---|---|
POST /mcp |
MCP protocol endpoint |
GET / |
Service information (JSON) |
GET /debug/pprof/* |
Profiling endpoints |
Development and advanced usage
Source build requirements
- Go 1.25+
- Nikto (
apt install niktoor equivalent) - Nuclei (
go install github.com/projectdiscovery/nuclei/v3/cmd/nuclei@latest) - Wapiti (
apt install wapitior equivalent) - Shcheck (
pip install shcheckor from GitHub) - SQLite3
# Clone the repository
git clone https://github.com/tb0hdan/wass-mcp.git
cd wass-mcp
# Build
make build
# Run
./build/wass-mcp
Starting the Server
# 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
| Flag | Default | Description |
|---|---|---|
--bind |
localhost:8989 |
HTTP server bind address |
--db |
./wass-mcp.db |
SQLite database file path |
--debug |
false |
Enable debug logging |
--version |
- | Print version and exit |
Linting
make lint
Testing
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
- Fork the repository
- Create a feature branch (
git checkout -b feature/new-tool) - Commit your changes (
git commit -am 'Add new scanning tool') - Push to the branch (
git push origin feature/new-tool) - Create a Pull Request
Acknowledgments
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。