In-depth architectural comparison of the Phishtank and ️ Not for Production Use! 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
Phishtank
Developer Tools · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
️ Not for Production Use!
Developer Tools · Local stdio
Quality: 37/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Phishtank if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose ️ Not for Production Use! if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
P
Choose Phishtank when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Check if a URL is a known phishing site in the PhishTank database. Returns whether it is a phish, verification status, and details URL. Example: check_url("http://suspicious-site.example.com/login").
️ Not for Production Use! Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
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).
Phishtank is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, ️ Not for Production Use! belongs to Developer Tools using local stdio subprocess. Select Phishtank when you need capabilities focused on developer tools and ️ Not for Production Use! when you require tools for developer tools.