What is the key difference between ParseAPI and Potarix Enricher?

ParseAPI belongs to the Communication category with local stdio execution, while Potarix Enricher belongs to the Communication category with local stdio execution.

How do I install ParseAPI or Potarix Enricher in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are ParseAPI and Potarix Enricher free or paid?

ParseAPI operates under a Free / Open Source model (No auth required). Potarix Enricher operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

ParseAPI lists 18 tools with 0 views and 0 GitHub stars. Potarix Enricher lists 9 tools with 1 views and 0 GitHub stars.

Can I use both ParseAPI and Potarix Enricher together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

ParseAPI vs Potarix Enricher

In-depth architectural comparison of the ParseAPI and Potarix Enricher 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

ParseAPI

Communication · Local stdio

Quality: 51/100 (Good) | Auth: No auth required

Potarix Enricher

Communication · Local stdio

Quality: 51/100 (Good) | Auth: No auth required

Verdict Summary: Choose ParseAPI if you need specialized Communication tools running via a local process. Choose Potarix Enricher if your workspace requires Communication integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose ParseAPI when:

You need dedicated capabilities in the Communication domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: PARSEAPI_KEY.
Primary tools included: stack, domain, dns.

Explore ParseAPI Details

Choose Potarix Enricher when:

You need dedicated capabilities in the Communication domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: POTARIX_API_KEY.
Primary tools included: lookup_company_website, find_person_email, find_decision_maker_email.

Feature & Specification Comparison

Specification	ParseAPI Communication	Potarix Enricher Communication
Summary	Official parseAPI MCP. Place, IP, email, phone, weather, currency lookups.	Find company websites and verified business emails through the Potarix Enricher API.
Category & Scope	Communication	Communication
Quality signal

Tools & Capabilities Breakdown

ParseAPI Tools (18)

stack

{"domain":"example.com"}` (website technologies and versions by category)

domain

{"domain":"example.com"}` (registration status)

dns

{"domain":"example.com","type":"TXT"}

{"domain":"example.com"}

asn

{"asn":"AS13335"}

mac

{"mac":"00:1B:63:84:45:E6"}

card

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).

ParseAPI Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "parseapi": {
      "command": "npx",
      "args": [
        "-y",
        "parseapi-mcp@1.6.0"
      ],
      "env": {
        "PARSEAPI_KEY": "YOUR_PARSEAPI_KEY_HERE"
      }
    }
  }
}

Potarix Enricher Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "potarix-enricher": {
      "command": "npx",
      "args": [
        "-y",
        "potarix-mcp"
      ],
      "env": {
        "POTARIX_API_KEY": "YOUR_POTARIX_API_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

ParseAPI is categorized under Communication and uses a local stdio subprocess. In contrast, Potarix Enricher belongs to Communication using local stdio subprocess. Select ParseAPI when you need capabilities focused on communication and Potarix Enricher when you require tools for communication.

More alternatives to ParseAPI More alternatives to Potarix Enricher Communication category hub