Run.pay vs ZadenWorks

In-depth architectural comparison of the Run.pay and ZadenWorks 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.

Which MCP Server Should You Choose?

Choose Run.pay when:

• You need dedicated capabilities in the Finance & Fintech domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: list_services, call_service.

Explore Run.pay Details

Z

Choose ZadenWorks when:

• You need dedicated capabilities in the Finance & Fintech domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore ZadenWorks Details

Feature & Specification Comparison

Specification	Run.pay Finance & Fintech	Z ZadenWorks Finance & Fintech
Summary
Category & Scope	Finance & Fintech	Finance & Fintech
Quality signal

Tools & Capabilities Breakdown

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

{
  "mcpServers": {
    "run-pay": {
      "command": "uvx",
      "args": [
        "requests"
      ]
    }
  }
}

{
  "mcpServers": {
    "zadenworks": {
      "url": "https://x402-zadenworks.zaden-gaming.workers.dev/"
    }
  }
}

Related MCP Server Comparisons