Polymarket Prediction… vs Graph Polymarket Mcp | AllMCPs
Side-by-Side Model Context Protocol Comparison
Polymarket Predictions Mcp vs Graph Polymarket Mcp
In-depth architectural comparison of the Polymarket Predictions Mcp and Graph Polymarket 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.
At a Glance & Executive Verdict
Polymarket Predictions Mcp
Finance & Fintech · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Graph Polymarket Mcp
Finance & Fintech · Local stdio
Quality: 44/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Polymarket Predictions Mcp if you need specialized Finance & Fintech tools running via a local process. Choose Graph Polymarket Mcp if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Polymarket Predictions Mcp 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).
Polymarket Predictions Mcp is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, Graph Polymarket Mcp belongs to Finance & Fintech using local stdio subprocess. Select Polymarket Predictions Mcp when you need capabilities focused on finance & fintech and Graph Polymarket Mcp when you require tools for finance & fintech.
Formatted string with event details (`title`, `description`, `endDate`, `volume`) and a table of markets (`question`, `closed`, `volume`, `outcomes`, `outcomePrices`).
condition_ids
List of condition IDs
Prompt
q
Search query (required)
+12 more tools listed on main page
Graph Polymarket Mcp Tools (31)
list_subgraphs
List all available Polymarket subgraphs with descriptions and key entities
get_subgraph_schema
Get the full GraphQL schema for a specific subgraph
query_subgraph
Execute a custom GraphQL query against any subgraph
get_market_data
Get market/condition data with outcomes and resolution status
get_global_stats
Get platform stats: market counts + real volume/fees/trades
get_account_pnl
Get a trader's P&L and performance metrics (winRate, profitFactor, maxDrawdown)
get_top_traders
Leaderboard ranked by PnL, winRate, volume, or profitFactor. Cross-refs Orderbook to flag rows where OB volume exceeds Beefy-tracked volume and surface OB-only traders absent from the leaderboard.
get_daily_stats
Daily volume, fees, trader counts, and market activity (1–90 days)
get_market_positions
Top holders for a specific outcome token with their P&L
get_user_positions
Current token positions. Cross-refs Orderbook: flags ⚠ orderbook-only entry when `totalBought=0` but OB volume exists, and ⚠ mixed entry when OB volume > 2× split collateral.
get_recent_activity
Unified chronological feed interleaving splits, merges, and redemptions with orderbook fills. Supports optional address filter.