streamable-httpMITupdated 12d ago
Model Context Protocol (MCP) server for phishunt.io.
¿Qué puedes hacer con Phishunt?
phishunt-mcp
Model Context Protocol (MCP) server for phishunt.io.
Exposes the public phishing-domains feed as MCP tools so AI agents can look up suspicious domains, list phishings by targeted brand, and sync detection deltas.
- Endpoint:
https://mcp.phishunt.io/(HTTP JSON-RPC 2.0, POST) - Protocol version: 2025-11-25
- Auth: none (data is CC0)
- License (data): CC0-1.0 · License (code): MIT
Tools
| Name | Purpose |
|---|---|
check_domain |
Is this domain/URL substring in the active phishunt feed? |
list_brand_phishings |
List active phishings targeting a brand (e.g. microsoft). |
get_recent_detections |
Delta sync: detections since an ISO date. |
get_brand_metadata |
Curated brand metadata (display name, category, AI characterisation, active count). |
get_cert_metadata |
Factual metadata for an abused TLS intermediate CA (operator, root, key type, siblings). |
search_phishings |
Free-text search across active phishing URLs/domains/IPs (min 3 chars). |
analyze_url |
Passive phishing-signal analysis of any URL/domain - returns a single adjudicated verdict (phishing / likely_phishing / suspicious / no_evidence / not_assessed) plus the supporting evidence (URL-shape heuristics, stored score/verdict if known, external-feed cross-reference, historical detections). Unknown suspicious domains are auto-queued for full analysis. |
analyze_url_deep |
ACTIVE deep analysis of a URL (contacts the target: HTTP + TLS cert + RDAP + NS + GeoIP, SOCKS5-isolated) and re-scores it with the full 5-layer engine. Slow (5-15s), token-gated, and rate-limited (shared 50/day budget, single-flight) — requires DEEP_TOKEN configured on this Worker; use only when analyze_url is inconclusive. |
get_related_infrastructure |
Find infrastructure/content overlap for a known indicator (shared IP, cert, nameservers, favicon, etc.); surfaces the possible campaign / suspected cluster it belongs to. |
get_campaigns |
List possible campaigns / suspected clusters (shared-infrastructure groupings), optionally filtered by brand or active-only. |
get_campaign |
Full detail for one possible campaign / suspected cluster: evidence breakdown, every member indicator, export links. |
Use with Claude Desktop / Claude.ai / other MCP clients
Add to your MCP client config:
{
"mcpServers": {
"phishunt": {
"url": "https://mcp.phishunt.io/"
}
}
}
Quick test
curl -sX POST https://mcp.phishunt.io/ \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"tools/list","id":1}' | jq .
Secrets
analyze_url_deep needs a DEEP_TOKEN Worker secret (the backend's
X-Phishunt-Deep-Token). Without it configured, the tool still appears in
tools/list but fails clean on tools/call — it never reaches the backend.
wrangler secret put DEEP_TOKEN
Develop
npm install
npm run dev # wrangler dev on http://localhost:8787
MCP_URL=http://localhost:8787 npm test
Deploy
npm run deploy # wrangler deploy
MCP_URL=https://mcp.phishunt.io npm test
Instalación
Añade Phishunt a tu cliente. Elige el que uses.
claude mcp add --transport http phishunt https://mcp.phishunt.io/codex mcp add phishunt --url https://mcp.phishunt.io/{
"mcpServers": {
"phishunt": {
"url": "https://mcp.phishunt.io/"
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"servers": {
"phishunt": {
"type": "http",
"url": "https://mcp.phishunt.io/"
}
}
}Add to `.vscode/mcp.json` in your workspace.
{
"mcpServers": {
"phishunt": {
"url": "https://mcp.phishunt.io/"
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"phishunt": {
"serverUrl": "https://mcp.phishunt.io/"
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
11 herramientas
Phishunt expone 11 herramientas a un agente conectado.
- check_domain
- Is this domain/URL substring in the active phishunt feed?
- list_brand_phishings
- List active phishings targeting a brand (e.g. `microsoft`).
- get_recent_detections
- Delta sync: detections since an ISO date.
- get_brand_metadata
- Curated brand metadata (display name, category, AI characterisation, active count).
- get_cert_metadata
- Factual metadata for an abused TLS intermediate CA (operator, root, key type, siblings).
- search_phishings
- Free-text search across active phishing URLs/domains/IPs (min 3 chars).
- analyze_url
- Passive phishing-signal analysis of any URL/domain - returns a single adjudicated `verdict` (phishing / likely_phishing / suspicious / no_evidence / not_assessed) plus the supporting evidence (URL-shape heuristics, stored score/verdict if known, external-feed cross-reference, historical detections). Unknown suspicious domains are auto-queued for full analysis.
- analyze_url_deep
- ACTIVE deep analysis of a URL (contacts the target: HTTP + TLS cert + RDAP + NS + GeoIP, SOCKS5-isolated) and re-scores it with the full 5-layer engine. Slow (5-15s), token-gated, and rate-limited (shared 50/day budget, single-flight) — requires `DEEP_TOKEN` configured on this Worker; use only when `analyze_url` is inconclusive.
- get_related_infrastructure
- Find infrastructure/content overlap for a known indicator (shared IP, cert, nameservers, favicon, etc.); surfaces the possible campaign / suspected cluster it belongs to.
- get_campaigns
- List possible campaigns / suspected clusters (shared-infrastructure groupings), optionally filtered by brand or active-only.
- get_campaign
- Full detail for one possible campaign / suspected cluster: evidence breakdown, every member indicator, export links.
Puntuación
74 / 100
Buena
- Documentación22/25
- Mantenimiento19/25
- Confianza13/20
- Capacidad8/15
- Instalación12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 4 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 11 tool(s) documented
- Provides prompt templates
- Provides resources
- 6 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Historial de versiones
| Versiones | Publicada |
|---|---|
| 0.1.0Última | 17 jul 2026 |