Shieldapi MCP vs Phishunt — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Shieldapi MCP vs Phishunt
In-depth architectural comparison of the Shieldapi MCP and Phishunt 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
Shieldapi MCP
Security · Local stdio
Quality: 56/100 (Good) | Auth: other
Phishunt
Security · Remote HTTP/SSE
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Shieldapi MCP if you need specialized Security tools running via a local process. Choose Phishunt if your workspace requires Security integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Shieldapi MCP when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Freemium).
You have access to required keys: SHIELDAPI_URL, SHIELDAPI_WALLET_PRIVATE_KEY.
Shieldapi MCP is categorized under Security and uses a local stdio subprocess. In contrast, Phishunt belongs to Security using remote streaming HTTP/SSE transport. Select Shieldapi MCP when you need capabilities focused on security and Phishunt when you require tools for security.
Run all security checks on a target (URL, domain, IP, or email). Most comprehensive scan.
scan_skill
Scan an AI agent skill/plugin for security issues across 8 risk categories (Snyk ToxicSkills taxonomy). Checks for prompt injection, malicious code, suspicious downloads, credential handling, secret detection, third-party content, unverifiable dependencies, and financial access patterns. Static analysis only — no code execution. Returns risk score (0-100), severity-ranked findings with file locations, and human-readable summary.
check_prompt
Detect prompt injection in text. Analyzes across 4 categories (direct injection, encoding tricks, exfiltration, indirect injection) with 200+ detection patterns. Designed for real-time inline usage before processing untrusted user input. Returns boolean verdict, confidence score (0-1), matched patterns with evidence, and decoded content if encoding obfuscation was detected. Response time <100ms p95.
check_mcp_trust
Get a multi-signal trust score for any MCP server endpoint. Analyzes security (domain reputation, SSL, SPF/DMARC), injection risk (tool description scanning), supply chain safety (toxic skill categories), reliability (uptime, latency, protocol compliance), and on-chain reputation (AgentProof ERC-8004). Returns composite trust score (0-100), tier (platinum/gold/silver/bronze/unranked), and detailed per-signal breakdown. Use this to evaluate whether an MCP server is safe to connect to.
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
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.