In-depth architectural comparison of the MCP Hn and MCP Pearch 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
MCP Hn
Search & Data Extraction · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
MCP Pearch
Search & Data Extraction · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: API Key required
Verdict Summary: Choose MCP Hn if you need specialized Search & Data Extraction tools running via a local process. Choose MCP Pearch if your workspace requires Search & Data Extraction integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Hn when:
You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Natural-language people search (e.g. *"software engineers in California with 5+ years Python"*). Supports fast/pro/superfast search types, contact reveal & contact filters, real-time profile refresh, insights, and thread-based pagination/follow-ups.
search_company_leads
Find companies and leads/contacts within them (B2B). Example: company *"AI startups in SF, 50–200 employees"* + leads *"CTOs and engineering managers"*, with optional personalized outreach messages.
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).
MCP Hn is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, MCP Pearch belongs to Search & Data Extraction using remote streaming HTTP/SSE transport. Select MCP Hn when you need capabilities focused on search & data extraction and MCP Pearch when you require tools for search & data extraction.