Oathscore vs Polymarket Wallet Intelligence

In-depth architectural comparison of the Oathscore and Polymarket Wallet Intelligence 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 Oathscore when:

• You need dedicated capabilities in the Finance & Fintech domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Freemium).
• Primary tools included: get_now, get_exchanges, get_volatility.

Explore Oathscore Details

P

Choose Polymarket Wallet Intelligence 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 Polymarket Wallet Intelligence Details

Feature & Specification Comparison

Specification	Oathscore moxiespirit Finance & Fintech	P Polymarket Wallet Intelligence Finance & Fintech
Summary	The trust layer for AI trading agents. Real-time world state (exchange status, VIX/VVIX/SKEW, economic events) in one call, plus independent quality ratings (0-100) for financial data APIs. 8 MCP tools.	Classify Polymarket wallets as human or bot, score their trading edge, read open positions.
Category & Scope	Finance & Fintech

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": {
    "moxiespirit-oathscore": {
      "command": "python",
      "args": [
        "oathscore_mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "polymarket-wallet-intelligence": {
      "command": "npx",
      "args": [
        "-y",
        "polymarket-wallet-intelligence"
      ]
    }
  }
}

Related MCP Server Comparisons