BlackDome Threat Intel

BlackDome MCP Server

Canonical MCP server name: io.github.blackdome-ai/blackdome-mcp

Package version: 0.4.0

Give your AI agents direct access to read-only observed threat intelligence. Look up attacker IPs, browse indicators of compromise (IOCs), inspect captured credentials and malware payloads, compare samples deterministically, inspect bounded evidence clusters, and retrieve authenticated ThreatDrop case and workflow status — all from Claude, Cursor, or any MCP-compatible client.

Community tools are free and need no API key. The tool table identifies the product features required for paid intelligence.

Quick Start

Option 1 — Separately hosted streamable-HTTP MCP (recommended, no install)

One hosted streamable-HTTP endpoint for compatible remote MCP clients (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 locally

Use uvx (part of uv) to fetch and run the server on demand:

uvx blackdome-mcp

For a fixed install, use pip install blackdome-mcp.

The free community tools use no API key. To unlock 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.

Feature gates: tool availability is enforced by the returned plan features, including api_access, stix_export, credential_intel or realtime_credential_feed, detonation_intel, session_intel, ioc_explanation, sample_compare, genome_clusters, and reproducible_novelty. ThreatDrop tools require a separate ThreatDrop product entitlement. 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." (candidate Enterprise/OEM pilot)
• "Pull the detonation report for sha256 a6713518f2e26745683d33ded61b465d0645d7af850464c559fba8bb84e68398." (Pro)
• "Explain the observed evidence for domain example.test." (Analyst)
• "Compare these two SHA-256 samples deterministically." (Pro)
• "Show the bounded evidence cluster for this IOC." (Pro)
• "What reproducible novelty does this URL show?" (Pro)
• "Show the ThreatDrop case state and takedown workflow status for submission 42." (ThreatDrop)

Environment Variables

The package runs locally over stdio; the separately hosted streamable-HTTP endpoint takes the key as an Authorization: Bearer header instead. The registry manifest declares only the package's stdio transport.

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. Current paid-plan limits are returned by whoami; candidate Enterprise/OEM pilots are contact-led and do not have fixed public limits. When you hit a limit the server returns a clear 429 error with retry timing.

Troubleshooting

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

Security

• Read-only. Tools use GET or semantically read-only JSON-body POST requests; none 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 credential_intel or realtime_credential_feed.
• 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.
• Customer intelligence. Retrieve observed evidence, deterministic comparisons, reproducible behavior assessments, case state and takedown-workflow status.

License

MIT