Run.pay vs Pop MCP

In-depth architectural comparison of the Run.pay and Pop MCP 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 remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: list_services, call_service.

Explore Run.pay Details

Choose Pop MCP 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).
• Primary tools included: pop_create_sdi_invoice, pop_create_peppol_invoice, pop_create_pdf_invoice.

Explore Pop MCP Details

Feature & Specification Comparison

Specification	Run.pay Finance & Fintech	Pop MCP Finance & Fintech
Summary	Stripe-native marketplace where AI agents discover and pay per call for API services.	Italian e-invoicing (FatturaPA/SdI), Peppol, and PDF invoice generation via POP
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": {
      "url": "https://runpay-backend-visibility-production.up.railway.app/mcp"
    }
  }
}

{
  "mcpServers": {
    "pop-mcp": {
      "url": "https://mcp.popapi.io/mcp"
    }
  }
}

Related MCP Server Comparisons