<!-- mcp-name: io.github.blackdome-ai/blackdome -->

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

Install

pip install blackdome-mcp

Configure

The free public tools work with no API key. To unlock the paid tiers (credential intelligence, payloads, actors, warboard, STIX export), get an API key at [https://blackdome.ai/pricing](https://blackdome.ai/pricing).

#### Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "blackdome": {
      "command": "blackdome-mcp",
      "env": {
        "BLACKDOME_API_KEY": "your-api-key-here"
      }
    }
  }
}

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

#### Claude Code

claude mcp add blackdome -- blackdome-mcp
# Optional — only needed for paid tools:
export BLACKDOME_API_KEY="your-api-key-here"

#### Cursor

Add to your MCP settings:

{
  "blackdome": {
    "command": "blackdome-mcp",
    "env": {
      "BLACKDOME_API_KEY": "your-api-key-here"
    }
  }
}

Available Tools

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

Plans: Community (free) → 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

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.

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