What is the key difference between Getregdata and Hungry eSIM?

Getregdata belongs to the Developer Tools category with local stdio execution, while Hungry eSIM belongs to the Developer Tools category with cloud HTTP/SSE execution.

How do I install Getregdata or Hungry eSIM 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 Getregdata and Hungry eSIM free or paid?

Getregdata operates under a Free / Open Source model (No auth required). Hungry eSIM operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Getregdata lists 0 tools with 0 views and 6 GitHub stars. Hungry eSIM lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Getregdata and Hungry eSIM 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

Getregdata vs Hungry eSIM

In-depth architectural comparison of the Getregdata and Hungry eSIM 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

Getregdata

Developer Tools · Local stdio

Quality: 47/100 (Fair) | Auth: No auth required

Hungry eSIM

Developer Tools · Remote HTTP/SSE

Quality: 36/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Getregdata if you need specialized Developer Tools tools running via a local process. Choose Hungry eSIM if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Getregdata when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Getregdata Details

Choose Hungry eSIM 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).

Explore Hungry eSIM Details

Feature & Specification Comparison

Specification	Getregdata Developer Tools	Hungry eSIM Developer Tools
Summary	Official business-registry data - KYC/AML, UBO, credit-risk, adverse media across 11 jurisdictions.	Travel eSIMs: unlimited data, pick your days, top up existing eSIMs, card checkout, no API key.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Getregdata Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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

Getregdata Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "getregdata": {
      "command": "npx",
      "args": [
        "-y",
        "skills"
      ]
    }
  }
}

Hungry eSIM Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "hungry-esim-2": {
      "url": "https://modelcontextprotocol.io"
    }
  }
}

Frequently Asked Questions

Getregdata is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Hungry eSIM belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Getregdata when you need capabilities focused on developer tools and Hungry eSIM when you require tools for developer tools.

More alternatives to Getregdata More alternatives to Hungry eSIM Developer Tools category hub