ThreatWatch MCP
Provides tools for analyzing IPs, domains, URLs, and hashes using VirusTotal's threat intelligence data.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ThreatWatch MCP Analyze IP 185.220.101.1 for threats"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
๐ก๏ธ ThreatWatch MCP
AI-Powered Threat Intelligence with Real-Time Alert Monitoring
A Model Context Protocol (MCP) server that brings multi-source threat intelligence directly into Claude Desktop and any MCP-compatible AI assistant.
โจ What Makes ThreatWatch Different
Feature | ThreatWatch | fastmcp-threatintel |
Real-time watch-list & alerts | โ | โ |
Persistent alert history | โ | โ |
Shodan InternetDB (free, no key needed) | โ | โ |
Status-change detection | โ | โ |
IOC extraction from freeform text | โ | โ |
Works with zero API keys | โ | โ |
Related MCP server: FastMCP ThreatIntel
๐ Available MCP Tools
Tool | Description |
| Analyse a single IP / domain / URL / hash |
| Analyse up to 50 IOCs concurrently |
| Extract IOCs from log files, reports, pastes |
| Add an IOC to the real-time watch-list |
| Remove an IOC from the watch-list |
| Show all monitored IOCs and their status |
| Retrieve alerts from monitored IOCs |
| Manually trigger a re-scan of all watches |
| Show configured sources and monitor state |
๐ Installation
Prerequisites
Python 3.11 or higher
API keys (see below โ all free tier)
Step 1 โ Clone the repo
git clone https://github.com/YOUR_USERNAME/threatwatch-mcp.git
cd threatwatch-mcpStep 2 โ Install
pip3 install fastmcp httpx python-dotenv
pip3 install -e .Step 3 โ Verify installation
which threatwatchYou should see a path like /usr/local/bin/threatwatch or
/Library/Frameworks/Python.framework/Versions/3.x/bin/threatwatch.
Copy this path โ you'll need it in Step 5.
๐ API Keys (All Free)
Source | Required | Free Limit | Sign Up |
VirusTotal | Recommended | 1,000 req/day | |
AlienVault OTX | Recommended | Unlimited | |
AbuseIPDB | Optional | 1,000 req/day | |
IPinfo | Optional | 50,000 req/month | |
Shodan InternetDB | None needed | Always free | Built-in |
ThreatWatch works with zero API keys โ Shodan InternetDB is always available and returns open ports, CVEs, and hostnames for any IP for free.
โ๏ธ Connect to Claude Desktop
Step 4 โ Open the Claude Desktop config
macOS:
open -e ~/Library/Application\ Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonStep 5 โ Add ThreatWatch
Add the threatwatch entry to your mcpServers block.
Replace the command path with the output of which threatwatch from Step 3,
and fill in your API keys:
{
"mcpServers": {
"threatwatch": {
"command": "/Library/Frameworks/Python.framework/Versions/3.13/bin/threatwatch",
"env": {
"VIRUSTOTAL_API_KEY": "your_virustotal_key_here",
"OTX_API_KEY": "your_otx_key_here",
"ABUSEIPDB_API_KEY": "your_abuseipdb_key_here",
"IPINFO_API_KEY": "your_ipinfo_key_here"
}
}
}
}If you already have other MCP servers configured, just add the
threatwatchblock inside your existingmcpServersobject โ don't replace the whole file.
Step 6 โ Restart Claude Desktop
Fully quit Claude Desktop (Cmd + Q on Mac, system tray โ Exit on Windows)
and reopen it.
Step 7 โ Verify
Click the "+" button at the bottom of the Claude chat โ Connectors. You should see ThreatWatch listed with all 9 tools.
Then test it:
Run server_status๐ฌ Example Prompts
Analyse IP 185.220.101.1 for threats
Check if domain update-adobe-flash.ru is malicious
Is this hash dangerous: d41d8cd98f00b204e9800998ecf8427e
Extract all IOCs from this log and analyse them:
[paste your firewall log, SIEM alert, or email header]
Add a watch on 185.220.101.1 and alert me if it becomes malicious
Get all alerts from the last hour
Run a full monitor cycle now๐ How Real-Time Monitoring Works
add_watch("185.220.101.1", alert_on=["malicious", "suspicious"])
โ
โผ
Watch-list saved to ~/.threatwatch/watchlist.json
โ
โผ
run_monitor_cycle() โ trigger manually or on a schedule
โ
โผ
Re-queries all sources for each watched IOC
โ
โผ
Status changed or threshold crossed?
โ
Yes โ No
โผ โผ
Alert (no-op)
โ
โผ
get_alerts(since_minutes=60)๐๏ธ Project Structure
threatwatch-mcp/
โโโ src/
โ โโโ threatwatch/
โ โโโ __init__.py โ package definition
โ โโโ server.py โ FastMCP server + all 9 MCP tools
โ โโโ config.py โ settings from environment variables
โ โโโ ioc_detector.py โ IOC type detection (IP/domain/URL/hash)
โ โโโ intel_sources.py โ API adapters (VT, OTX, AbuseIPDB, IPinfo, Shodan)
โ โโโ alert_monitor.py โ real-time watch-list + alert engine
โ โโโ reporter.py โ Markdown report builder
โโโ tests/
โ โโโ test_core.py โ unit tests
โโโ pyproject.toml โ package config + dependencies
โโโ .env.example โ environment variable template
โโโ README.md๐ Security Notes
Never commit your
.envfile โ it is in.gitignoreby defaultRestrict config file permissions on your machine:
chmod 600 ~/Library/Application\ Support/Claude/claude_desktop_config.jsonAll API keys used are read-only โ they can query data but cannot modify anything
If a key is ever leaked, regenerate it instantly from each service's dashboard
๐งช Running Tests
pip3 install pytest pytest-asyncio
pytest tests/ -v๐ License
Apache 2.0 โ see LICENSE for details.
๐ Acknowledgments
FastMCP โ the MCP framework that powers ThreatWatch
fastmcp-threatintel โ original inspiration
VirusTotal, AlienVault OTX, AbuseIPDB, IPinfo, Shodan โ threat intelligence sources
Available Tools
9 toolsadd_watchAdd WatchA
Add an IOC to the real-time watch-list. ThreatWatch will periodically re-scan it and flag changes in threat status.
Inputs: ioc (required), label, alert_on. Returns: result
analyze_iocAnalyze IocB
Analyse a single Indicator of Compromise (IOC) across all available threat intelligence sources.
Supports: IPv4/IPv6 addresses, domain names, URLs, MD5/SHA1/SHA256 hashes.
Inputs: ioc (required), include_raw. Returns: result
bulk_analyzeBulk AnalyzeB
Analyse multiple IOCs concurrently and return a consolidated summary.
Inputs: iocs (required), max_concurrent. Returns: result
detect_iocs_in_textDetect Iocs In TextA
Extract all IOCs (IPs, domains, URLs, hashes) from freeform text such as log files, incident reports, or paste-bin content.
Inputs: text (required), auto_analyze. Returns: result
get_alertsGet AlertsC
Retrieve alerts generated by the real-time monitor for watched IOCs.
Inputs: severity, mark_read, since_minutes. Returns: result
list_watchesList WatchesA
List all IOCs currently on the watch-list with their last-known status.
Returns: Markdown table of watched IOCs.
Inputs: no named parameters. Returns: result
remove_watchRemove WatchC
Remove an IOC from the real-time watch-list.
Inputs: watch_id (required). Returns: result
run_monitor_cycleRun Monitor CycleA
Manually trigger a monitoring cycle โ re-scans all watched IOCs immediately rather than waiting for the next scheduled interval.
Returns: Summary of how many IOCs were checked and how many triggered alerts.
Inputs: no named parameters. Returns: result
server_statusServer StatusA
Return the current ThreatWatch server status including configured API sources, watch-list size, and pending alert count.
Returns: A Markdown status card.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: status, single analysis, bulk analysis, watch management, alert retrieval, manual monitor, and text extraction. No overlap between tools; an agent can easily select the right one based on the action and resource.
All tool names follow a consistent verb_noun pattern (e.g., analyze_ioc, add_watch, get_alerts) or noun_status pattern (server_status), with clear and predictable naming throughout.
With 9 tools, the set is well-scoped for a threat intelligence watch server, covering analysis, watch-list management, monitoring, and alerting without redundancy.
The tool surface provides complete lifecycle coverage: analyze IOCs (single/bulk), manage watch-list (add/remove/list), monitor (manual/automatic), retrieve alerts, and extract IOCs. No obvious gaps for the stated purpose.
Related MCP Connectors
AI-powered threat intelligence, smart contract auditing, and cybersecurity OSINT.
Real-time threat intel for AI agents: 890K+ IOCs incl. prompt-injection & AI-skill threats
Enrich, search, assess, and manage threat intelligence through 80+ typed MCP tools.
Security intelligence for AI agents. 27 x402 endpoints: honeypot, forensics, CAPTCHA, preflight.
Related MCP Servers
- -licenseNot gradedqualityNot gradedmaintenanceEnterprise network analysis platform that enables AI-powered packet analysis, threat detection, and network security capabilities through Claude Desktop integration.1-
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered threat intelligence analysis of IPs, domains, URLs, and file hashes across multiple threat intelligence platforms (VirusTotal, AlienVault OTX, AbuseIPDB, IPinfo) with APT attribution and interactive reporting through natural language queries.28 PyPI40Apache 2.0
- AlicenseCqualityDmaintenanceAn AI-powered penetration testing server that integrates over 30 security tools with Groq LLM analysis for automated vulnerability scanning, triage, and reporting. It enables users to perform comprehensive security assessments through natural language natively within Claude Desktop.29MIT
- FlicenseNot gradedqualityDmaintenanceThis MCP server connects Claude Desktop to OpenCTI for AI-augmented threat intelligence analysis, enabling natural language queries and instant, contextualized answers from your threat intelligence database.29-