Kali Linux MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MULLVAD_ACCOUNT_NUMBER | No | Your Mullvad account number (16 digits) | |
| MULLVAD_DEFAULT_SERVER | No | Default Mullvad server location | se |
| MULLVAD_DEFAULT_PROTOCOL | No | Default VPN protocol (wireguard or openvpn) | wireguard |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nmap_scanB | Perform network scanning with Nmap to discover hosts, ports, and services |
| nikto_scanC | Scan web servers for vulnerabilities and misconfigurations with Nikto |
| dirb_scanB | Brute-force discover hidden directories and files on web servers with DIRB |
| sqlmap_scanC | Test for SQL injection vulnerabilities with SQLMap |
| zap_scanB | Comprehensive web application security scanner using OWASP ZAP |
| testssl_scanB | Test SSL/TLS configuration and vulnerabilities with testssl.sh |
| nuclei_scanC | Fast vulnerability scanner using community templates with Nuclei |
| retirejs_scanB | Scan for vulnerable JavaScript libraries with retire.js |
| security_headers_checkB | Check HTTP security headers configuration for best practices |
| vpn_connectB | Connect to Mullvad VPN for anonymous security testing |
| vpn_disconnectB | Disconnect from Mullvad VPN |
| vpn_statusB | Check current VPN connection status and server information |
| jwt_decodeB | Decode and analyze JWT tokens, optionally verifying signatures |
| jwt_security_testB | Test JWT token for security vulnerabilities (none algorithm, weak secrets) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Tools are mostly distinct—each targets a specific security task (web scanning, JWT, SSL, VPN, etc.). Some overlap exists among web scanners (dirb, nikto, nuclei, zap), but descriptions clarify their different foci. Only minor potential confusion between nikto and nuclei.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., dirb_scan, vpn_connect, jwt_decode). The few variations like jwt_security_test still use the same structure, so naming is predictable and uniform.
With 14 tools, the set is well-scoped for a security testing server. It covers a range of essential tasks (network scanning, web application scanning, JWT analysis, VPN management) without being overwhelming or too sparse.
The tool set covers major security testing areas: network scanning (nmap), web vuln scanning (multiple tools), SQL injection (sqlmap), SSL (testssl), JWT, directory brute-force, JS library vulns, and security headers. Minor gaps like exploitation or password cracking exist, but core workflows are covered.