In-depth architectural comparison of the Lpxpoly 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
Lpxpoly MCP
Finance & Fintech · Local stdio
Quality: 52/100 (Good) | Auth: API Key required
Graph Polymarket MCP
Finance & Fintech · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose Lpxpoly 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 Lpxpoly MCP when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Paid Service).
You have access to required keys: LIGHTNINGPROX_SPEND_TOKEN.
Polymarket prediction market analysis via LightningProx. Find mispriced markets, analyze specific markets, get top markets by volume. Pay per request with Bitcoin Lightning spend tokens.
Polymarket prediction market data via The Graph — markets, positions, orders, user activity, and real-time odds.
Category & Scope
Tools & Capabilities Breakdown
Lpxpoly MCP Tools (4)
get_edge_opportunities
Find mispriced markets with AI edge
analyze_market
Deep analysis of a specific market
get_top_markets
Browse top markets by volume
check_balance
Check your Lightning balance
Graph Polymarket MCP Tools (35)
list_subgraphs
List all available Polymarket subgraphs with descriptions and key entities
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).
Lpxpoly 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 Lpxpoly MCP when you need capabilities focused on finance & fintech and Graph Polymarket MCP when you require tools for finance & fintech.
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.