Drive a self-hosted Darkmoon Pro AI pentest instance: start runs, read campaigns and findings.
A Model Context Protocol server that lets an MCP client (Claude Desktop, Goose, Continue, LibreChat, ...) drive Darkmoon, an open source (GPL-3.0) autonomous AI penetration testing platform.
The Darkmoon engine and CLI are open source. This server talks to the Darkmoon Dashboard API, which is part of Darkmoon Pro and always self-hosted: there is no public hosted endpoint, so you supply the base URL of your own instance. It does not work against the open source CLI alone.
| Tool | Description |
|---|---|
run_pentest | Start an autonomous pentest against one authorized target and return the run_id |
get_run_status | Report running, completed, error or unknown for a run, from its run log |
list_campaigns | List campaigns visible to the dashboard user (read only) |
get_findings | Vulnerabilities and severity statistics for a campaign (read only) |
Only run assessments against systems you own or are explicitly authorized in writing to test. Findings can include false positives and must be reviewed by a qualified human.
| Variable | Description |
|---|---|
DARKMOON_BASE_URL | Base URL of your Darkmoon Pro Dashboard API (required) |
DARKMOON_USERNAME, DARKMOON_PASSWORD | Dashboard credentials; a JWT is requested on each call and never cached |
DARKMOON_TOKEN | Alternative to username/password: a pre-issued JWT |
DARKMOON_TIMEOUT_MS | Optional per-request timeout, default 60000 |
Claude Desktop (claude_desktop_config.json), Continue and LibreChat use the same mcpServers shape:
{
"mcpServers": {
"darkmoon": {
"command": "npx",
"args": ["-y", "@darkmoon_ai/mcp-server"],
"env": {
"DARKMOON_BASE_URL": "https://darkmoon.example.internal",
"DARKMOON_USERNAME": "your-dashboard-user",
"DARKMOON_PASSWORD": "your-dashboard-password"
}
}
}
}
Goose (~/.config/goose/config.yaml):
extensions:
darkmoon:
type: stdio
enabled: true
name: darkmoon
cmd: npx
args: ["-y", "@darkmoon_ai/mcp-server"]
envs:
DARKMOON_BASE_URL: https://darkmoon.example.internal
DARKMOON_USERNAME: your-dashboard-user
DARKMOON_PASSWORD: your-dashboard-password
Continue (.continue/mcpServers/darkmoon.yaml):
name: Darkmoon
version: 0.1.0
schema: v1
mcpServers:
- name: darkmoon
command: npx
args: ["-y", "@darkmoon_ai/mcp-server"]
env:
DARKMOON_BASE_URL: https://darkmoon.example.internal
DARKMOON_USERNAME: your-dashboard-user
DARKMOON_PASSWORD: your-dashboard-password
npm install
npm run build
npm test # mocked Dashboard API, in-memory MCP client and a real stdio process
GPL-3.0-only, same as Darkmoon.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @darkmoon_ai/mcp-serverMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-ascit31-darkmoon-mcp-server": {
"command": "npx",
"args": [
"-y",
"@darkmoon_ai/mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@darkmoon_ai/mcp-servernpmDarkmoon works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.