In-depth architectural comparison of the Phishunt and Shield MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Phishunt
Security · Remote HTTP/SSE
Quality: 52/100 (Good) | Auth: No auth required
Shield
Security · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Verdict Summary: Choose Phishunt if you need specialized Security tools running via a hosted cloud SSE transport. Choose Shield if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Phishunt when:
You need dedicated capabilities in the Security domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Public phishing feed: suspicious/confirmed phishing URLs detected hourly. No auth, CC0.
Local guardrail proxy for AI coding agents. Wraps any MCP server (stdio or Streamable HTTP) and blocks destructive tool calls — DROP TABLE, rm -rf, force-push — before they execute. MCP supply-chain protection: TOFU tool-catalog pinning against rug pulls, plus tool-description and tool-result scanning for tool poisoning and prompt injection. 51 starter rules, approval gates, audit logging. Single binary, Apache-2.0.
Category & Scope
Tools & Capabilities Breakdown
Phishunt Tools (11)
check_domain
Is this host (or a list of up to 20) in the active phishunt feed? Exact match; misses are checked against the archive.
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
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Phishunt is categorized under Security and uses a remote streaming HTTP/SSE transport. In contrast, Shield belongs to Security using local stdio subprocess. Select Phishunt when you need capabilities focused on security and Shield when you require tools for security.
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)…
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…
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.