What is the key difference between Getregdata and Pipeworx?

Getregdata belongs to the Developer Tools category with local stdio execution, while Pipeworx belongs to the Developer Tools category with local stdio execution.

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

Getregdata operates under a Free / Open Source model (No auth required). Pipeworx 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. Pipeworx lists 0 tools with 0 views and 0 GitHub stars.

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

In-depth architectural comparison of the Getregdata and Pipeworx 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: 45/100 (Fair) | Auth: No auth required

Pipeworx

Developer Tools · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Getregdata if you need specialized Developer Tools tools running via a local process. Choose Pipeworx 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?

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 Pipeworx 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 Pipeworx Details

Feature & Specification Comparison

Specification	Getregdata Developer Tools	P Pipeworx Developer Tools
Summary	Official business-registry data - KYC/AML, UBO, credit-risk, adverse media across 11 jurisdictions.	Live data gateway for AI — 3,300+ tools across 750+ sources, with citations
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.

Pipeworx 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"
      ]
    }
  }
}

Pipeworx Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Getregdata is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Pipeworx belongs to Developer Tools using local stdio subprocess. Select Getregdata when you need capabilities focused on developer tools and Pipeworx when you require tools for developer tools.

More alternatives to Getregdata More alternatives to Pipeworx Developer Tools category hub