MCP Pear vs Xrpl Referee

In-depth architectural comparison of the MCP Pear and Xrpl Referee 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 MCP Pear 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).
• Primary tools included: get_health, list_markets, get_active_markets.

Explore MCP Pear Details

Choose Xrpl Referee 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).
• Primary tools included: create_agent_wallet, fund_xrpl_wallet_via_coinbase, post_job.

Explore Xrpl Referee Details

Feature & Specification Comparison

Specification	MCP Pear Developer Tools	Xrpl Referee Developer Tools
Summary	MCP server for Pear Protocol: markets, positions, orders, portfolio, and gated trade execution.	Trust and payment layer for the agentic economy on the XRP Ledger.
Category & Scope	Developer Tools	Developer Tools
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": {
    "mcp-pear": {
      "command": "npx",
      "args": [
        "-y",
        "@marvelcodes/mcp-pear@latest"
      ]
    }
  }
}

{
  "mcpServers": {
    "xrpl-referee": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli@latest",
        "run",
        "xrpl/agent-trust",
        "--key",
        "YOUR_SMITHERY_KEY"
      ]
    }
  }
}

Related MCP Server Comparisons