AgentPay vs Paid MCP Metering

In-depth architectural comparison of the AgentPay and Paid MCP Metering 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?

A

Choose AgentPay 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: xhs_get_note_detail, xhs_get_user_notes, china_wholesale_pricing_query.

Explore AgentPay Details

Choose Paid MCP Metering 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).

Explore Paid MCP Metering Details

Feature & Specification Comparison

Specification	A AgentPay Finance & Fintech	Paid MCP Metering Finance & Fintech
Summary	x402 micropayments MCP: Xiaohongshu notes and paid APIs settled in USDC on Base.	Metered MCP tools: free discovery over MCP; per-call execution settled in USDC via x402 v2.
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": {
    "agentpay-8": {
      "command": "uvx",
      "args": [
        "mcp-server-agentpay"
      ]
    }
  }
}

{
  "mcpServers": {
    "paid-mcp-metering": {
      "command": "npx",
      "args": [
        "-y",
        "paid-mcp-metering"
      ]
    }
  }
}

Related MCP Server Comparisons