Limitless Subgraphs + MCP Server

Subgraphs and MCP server for Limitless Exchange prediction markets on Base.

Why Subgraphs?

The Limitless REST API is useful for market metadata (titles, descriptions, categories) but has significant limitations for analytics:

• Rate limited — max 2 concurrent requests, 300ms minimum delay between calls, 429s on bursts
• No historical aggregation — no way to query total protocol volume, trade counts over time, or cross-market analytics
• No on-chain depth — the API doesn't expose individual trade fills, position balances, splits/merges/redemptions, or resolution payouts

Subgraphs solve all of this. They index every on-chain event into a queryable GraphQL API with no rate limits, full historical data, and flexible aggregation. The MCP server combines both — subgraphs for the heavy analytics, REST API for market names and metadata.

Why market names aren't in the subgraphs

Market titles and descriptions are stored off-chain in the Limitless database — they are not emitted in any on-chain event. Unlike Polymarket, which uses UMA's QuestionInitialized event to embed question text in ancillaryData on-chain, Limitless uses a GnosisSafe multisig as the oracle address. The multisig calls prepareCondition directly on the CTF contract with no accompanying event that carries the question text. The questionId in the CTF's ConditionPreparation event is a bytes32 hash, not readable text.

This means there is no on-chain source a subgraph can index for market names. The MCP server bridges this gap by joining subgraph data (via conditionId) with the Limitless REST API for titles and metadata.

Subgraphs

Two subgraphs indexing different exchange venues on the same CTF (Conditional Tokens Framework):

Both share the same CTF contract (0xC9c9...) for conditions, positions, splits, merges, and redemptions. Each indexes its own set of exchange contracts for markets and trades.

Entities

• Condition — prepared markets with oracle, resolution status, payouts
• Market / NegRiskMarket — exchange-registered markets with volume, trade counts, fees
• Trade (immutable) — individual order fills with maker/taker, price, USD amounts
• UserPosition — per-user token balances and PnL
• Split / Merge / Redemption (immutable) — CTF liquidity events
• User — aggregated trader stats
• MarketDailySnapshot / GlobalDailySnapshot — daily time series
• GlobalStats — protocol-wide singleton

Contracts

Simple Markets:

NegRisk Markets:

Example Queries

# Global stats
{
  globalStats(id: "0x73696d706c65") {
    totalMarkets resolvedMarkets totalTradesCount
    totalVolumeUSD totalFeesUSD totalUsers
  }
}

# Recent trades with market info
{
  trades(first: 10, orderBy: timestamp, orderDirection: desc) {
    type maker taker amountUSD price venue timestamp
    market { id tradesCount volumeUSD }
  }
}

# User positions
{
  userPositions(where: { user: "0x..." , balance_gt: "0" }) {
    tokenId balance netCostUSD realizedPnlUSD
    condition { id resolved payoutNumerators }
  }
}

MCP Server

An MCP server that combines both subgraphs with the Limitless REST API for market names and metadata. Every tool queries the subgraphs for on-chain data.

Tools (18)

Setup

cd mcp-server
npm install
npm run build

Claude Code Config

{
  "mcpServers": {
    "limitless": {
      "command": "node",
      "args": ["/path/to/limitless-subgraphs/mcp-server/build/index.js"],
      "env": {
        "GRAPH_API_KEY": "your_graph_api_key",
        "LIMITLESS_API_KEY": "lmts_your_key_here"
      }
    }
  }
}

API Keys

• GRAPH_API_KEY (required) — needed to query the subgraphs via The Graph. Get one at thegraph.com/studio/apikeys
• LIMITLESS_API_KEY (optional) — enables market name/metadata enrichment from the Limitless REST API. Without it, market browsing and search still work (public endpoints). Generate one at limitless.exchange → profile menu → Api keys. Key format: lmts_.... Pass via X-API-Key header. See the Limitless API docs for full details.

Note: The Limitless REST API is rate limited to 2 concurrent requests with 300ms minimum delay. The subgraphs have no such limits, which is why the MCP routes all analytics queries through them and only uses the REST API for metadata.