Phishunt vs Vorim MCP Server — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Phishunt vs Vorim MCP Server
In-depth architectural comparison of the Phishunt and Vorim MCP Server 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
Vorim MCP Server
Security · Local stdio
Quality: 60/100 (Good) | Auth: API Key required
Verdict Summary: Choose Phishunt if you need specialized Security tools running via a hosted cloud SSE transport. Choose Vorim MCP Server 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).
Phishunt is categorized under Security and uses a remote streaming HTTP/SSE transport. In contrast, Vorim MCP Server belongs to Security using local stdio subprocess. Select Phishunt when you need capabilities focused on security and Vorim MCP Server 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.
Vorim MCP Server Tools (19)
vorim_ping
Check API health and connectivity
vorim_register_agent
Register a new agent with Ed25519 cryptographic identity
vorim_register_ephemeral
Register a `did:key` ephemeral agent with TTL
vorim_get_agent
Get agent details by ID
vorim_list_agents
List all agents with pagination and filtering
vorim_update_agent
Update agent metadata (name, description, status)
vorim_revoke_agent
Permanently revoke an agent
vorim_check_permission
Check if agent has a permission scope (sub-5ms)
vorim_grant_permission
Grant a permission with optional expiry and rate limits