# @darkmoon_ai/mcp-server

Drive a self-hosted Darkmoon Pro AI pentest instance: start runs, read campaigns and findings.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.1.0
- **Author:** io.github.ASCIT31
- **License:** GPL-3.0-only
- **npm:** @darkmoon_ai/mcp-server
- **Source:** https://github.com/ASCIT31/darkmoon-mcp-server
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 2 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-10T13:36:43.295Z
- **Version scanned:** 0.1.0
- **CVEs:** none found by OSV at scan time

## Tools

4 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `run_pentest` — Start an autonomous Darkmoon penetration test against one authorized target. The run executes in the background and can take a long time. Returns the run_id; po
- `get_run_status` — Report whether a Darkmoon run is 'running', 'completed', 'error' or 'unknown' (run log not found), with the event count and the 5 most recent events.
- `list_campaigns` — List the Darkmoon campaigns visible to the dashboard user, with ids and status. Use a campaign id with get_findings.
- `get_findings` — Return the vulnerabilities and aggregated severity statistics for a Darkmoon campaign (read only). Each finding carries title, severity, CVSS score, category, s

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-server\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@darkmoon_ai/mcp-server\"\n      ],\n      \"env\": {\n        \"DARKMOON_PASSWORD\": \"<YOUR_DARKMOON_PASSWORD>\",\n        \"DARKMOON_TOKEN\": \"<YOUR_DARKMOON_TOKEN>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `DARKMOON_PASSWORD` — Darkmoon Password (optional)
- `DARKMOON_TOKEN` — Darkmoon Token (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 2 credentials (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 25, ceiling 25 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40darkmoon_ai%2Fmcp-server
- Install plan: https://forgeregistry.com/api/v1/packages/%40darkmoon_ai%2Fmcp-server/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40darkmoon_ai%2Fmcp-server
- HTML page: https://forgeregistry.com/registry/%40darkmoon_ai%2Fmcp-server
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.