BlackDome MCP Server

Give your AI agents direct access to live honeypot threat intelligence. Look up attacker IPs, browse indicators of compromise (IOCs), inspect captured credentials and malware payloads, profile threat actors, and render a real-time global attack map — all from Claude, Cursor, or any MCP-compatible client.

Most tools are free and need no API key (the public community tier). A subset of high-value intelligence requires a paid plan.

Quick Start

Option 1 — Cloud MCP (recommended, no install)

One URL, works in every client that supports remote MCP (Claude Desktop, the claude.ai web app, mobile, Cursor):

https://api.blackdome.ai/mcp

Free tools work with no key. To unlock the paid tiers (credential intelligence, payloads, actors, warboard, STIX export), get an API key at https://blackdome.ai/pricing and add it as an Authorization header:

{
  "mcpServers": {
    "blackdome-cloud": {
      "url": "https://api.blackdome.ai/mcp",
      "headers": {
        "Authorization": "Bearer bd_your_key_here"
      }
    }
  }
}

Option 2 — Run it locally

Use uvx (part of uv) — it fetches and runs the server on demand, with no separate install step and no PATH issues:

uvx blackdome-mcp

Prefer a fixed install? pip install blackdome-mcp works too — but note the troubleshooting item at the bottom if your client says "command not found".

The free public tools work with no API key. To unlock the paid tiers, get a key at https://blackdome.ai/pricing.

Claude Desktop

Merge this into claude_desktop_config.json — ~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows — then restart Claude:

{
  "mcpServers": {
    "blackdome": {
      "command": "uvx",
      "args": ["blackdome-mcp"],
      "env": {
        "BLACKDOME_API_KEY": "bd_your_key_here"
      }
    }
  }
}

The env block is optional — omit BLACKDOME_API_KEY to run free public tools only.

Claude Code

One command — the key is stored in the MCP config, so there are no shell exports to maintain (a plain export BLACKDOME_API_KEY=... only lasts for that terminal session, and your paid tools would stop working in the next one):

claude mcp add blackdome -e BLACKDOME_API_KEY=bd_your_key_here -- uvx blackdome-mcp

For free tools only:

claude mcp add blackdome -- uvx blackdome-mcp

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):

{
  "blackdome": {
    "command": "uvx",
    "args": ["blackdome-mcp"],
    "env": {
      "BLACKDOME_API_KEY": "bd_your_key_here"
    }
  }
}

API Key Behavior

• No key: free community tools work; paid tools return an explicit 401.
• Invalid key: paid tools (and whoami) fail loudly with 401 Invalid API key — there is no silent fallback to free-tier results. Free tools keep working regardless of key validity.
• Expired key / cancelled plan: 403 API key has expired / 403 Tenant account is inactive — again explicit errors, not degraded data.
• Valid key, wrong plan: a tool whose feature your plan does not include returns an explicit 403; check your granted features any time with whoami.

If a paid tool returns less than expected, run whoami first — it reports your plan, features, and live quota.

Available Tools

Free tools work with no key. Paid tools require an API key whose plan includes the listed feature.

Plans: Community (free) → Analyst ($49, real-time intel) → Pro ($299, adds stix_export, api_access, detonation_intel) → Enterprise ($2000, adds credential_intel, bulk_api, session_intel) → OEM ($5000). See pricing.

Example Prompts

Once connected, try asking your AI assistant:

• "Who are the top attackers hitting the honeypots this month?"
• "Look up attacker IP 176.65.139.56 and summarize what they tried."
• "Show me the latest malicious sha256 IOCs from the last week."
• "What are the IOC trends — which MITRE techniques are spiking?"
• "Render a heatmap of where attacks are coming from."
• "Export the IOC feed as CSV so I can load it into my SIEM."
• "What plan am I on and which features do I have?" (runs whoami)
• "Search captured SSH credentials for the username root." (paid)
• "Show me the most active hand-keyed attacker sessions this week." (Enterprise)
• "Pull the detonation report for sha256 a6713518f2e26745683d33ded61b465d0645d7af850464c559fba8bb84e68398." (Pro)

Environment Variables

Local (stdio) server only — the cloud endpoint takes the key as an Authorization: Bearer header instead.

Rate Limits

The free community tier is capped at roughly 30 requests/minute and 100 requests/day, and community IOC data carries a 72-hour freshness delay. Paid plans raise these limits substantially (Enterprise: 1000 req/min, 50,000 req/day). When you hit a limit the server returns a clear 429 error with retry timing. Use whoami to see your live quota.

Troubleshooting

• "command not found" in a GUI client: GUI apps don't load your shell PATH. Easiest fix: use "command": "uvx", "args": ["blackdome-mcp"] as shown above. If you pip-installed instead, run which blackdome-mcp (macOS/Linux) or where blackdome-mcp (Windows) and paste the full path into the command field.
• Paid tools return 401/403: see API Key Behavior — errors are explicit, and whoami tells you exactly what your key grants.

Security

• Read-only. Every tool is a GET request — the server never mutates BlackDome data.
• Keyless free tier. Public tools require no API key and expose only community-tier data.
• Masked credentials. The free lookup_attacker_ip tool masks captured passwords to ******** before returning them; credential_preview is masked server-side. Plaintext passwords are returned only by the paid search_credentials tool, which requires the credential_intel feature.
• Secrets stay local. Your API key is read from the environment and sent only to the BlackDome API over HTTPS. No data is stored by the MCP server — it proxies directly to BlackDome.

License

MIT