Icypeas vs Potarix Enricher
A side-by-side look at the Icypeas and Potarix Enricher MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
I
IcypeasCommunication · Local subprocess (stdio)Icypeas MCP — wraps the Icypeas email-search API (icypeas.com)40FairAuth: api key requiredVerdict: choose Icypeas for communication work as a local process; choose Potarix Enricher for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
IChoose Icypeas when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
Choose Potarix Enricher when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
POTARIX_API_KEY. - You want tools like
lookup_company_website, find_person_email, find_decision_maker_email.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | I Icypeas | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 40/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | None listed | POTARIX_API_KEY |
| Verified owner |
Tools & capabilities
Icypeas tools
No tool names declared yet. Check the project README from the listing page.
Potarix Enricher tools 9
lookup_company_websitecompany name → website URLfind_person_emailnamed person + company/domain → verified emailfind_decision_maker_emailcategory + domain → likely buyer name + emailfind_linkedin_emailLinkedIn profile URL → verified emailfind_company_emailsdomain → public company contact rosterfind_allone company name → website + DMs + full company email listcheck_balancecredits, email, saved-card status, key countstart_checkoutget a Stripe URL to add a card the first timetopup_creditscharge the saved card and add credits
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Icypeas
{
"mcpServers": {
"icypeas": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-icypeas"
]
}
}
}
Potarix Enricher
{
"mcpServers": {
"potarix-enricher": {
"command": "npx",
"args": [
"-y",
"potarix-mcp"
],
"env": {
"POTARIX_API_KEY": "YOUR_POTARIX_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Icypeas is categorized under Communication and uses a local stdio subprocess. Potarix Enricher belongs to Communication and uses a local stdio subprocess. Pick Icypeas for communication work and Potarix Enricher for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Icypeas is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Potarix Enricher has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add icypeas and potarix-enricher as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Icypeas has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Potarix Enricher has 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.