Polymarket Wallet Intelligence

Name: Polymarket Wallet Intelligence
Author: aemery13

by aemery13version 1.0.1i★ –iComputer or cloud

Registry nameio.github.aemery13/polymarket-intel

Install

Overview

Description from the maker (original English)

Classify Polymarket wallets as human or bot, score their trading edge, read open positions.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Accounting, finance & tax
You need to fill in: POLYMARKET_INTEL_API_KEY, X-API-Key

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: POLYMARKET_INTEL_API_KEY, X-API-Key

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "polymarket-intel": {
      "command": "uvx",
      "args": [
        "polymarket-intel-mcp"
      ],
      "env": {
        "POLYMARKET_INTEL_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http polymarket-intel https://polymarket-intel-production.up.railway.app/mcp --header 'X-API-Key: your-value'

Or run it on your computer

claude mcp add polymarket-intel --env POLYMARKET_INTEL_API_KEY=your-value -- uvx polymarket-intel-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "polymarket-intel": {
      "url": "https://polymarket-intel-production.up.railway.app/mcp",
      "headers": {
        "X-API-Key": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "polymarket-intel": {
      "command": "uvx",
      "args": [
        "polymarket-intel-mcp"
      ],
      "env": {
        "POLYMARKET_INTEL_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "polymarket-intel": {
      "type": "http",
      "url": "https://polymarket-intel-production.up.railway.app/mcp",
      "headers": {
        "X-API-Key": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "polymarket-intel": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "polymarket-intel-mcp"
      ],
      "env": {
        "POLYMARKET_INTEL_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

POLYMARKET_INTEL_API_KEY secret env
Optional API key for higher rate limits and paid features. Anonymous access works at free-tier limits.
X-API-Key secret HTTP header
Optional API key for higher rate limits.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account aemery13, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Accounting, finance & taxi

More stars than 0% of the other 1732 servers in this category
Published to the registry more recently than 8% of the other 1732 servers in this category
Basic checks equal to or better than 100% of the other 1732 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Polymarket Wallet Intelligence safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: POLYMARKET_INTEL_API_KEY, X-API-Key

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 6 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Finance Toolkit, SolidInvoice, Korea Tax Calculator

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Finance Toolkit

by JerBouma

500+ transparent financial methods calculated from raw statements, not third-party endpoints.

Computer or cloud★ 5,496MITUpdated today

Install

SolidInvoice

by SolidInvoice

Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.

Runs in the cloud★ 981MITUpdated 8 days ago

Install

Korea Tax Calculator

by UpstageAI

Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.

Runs on your computer★ 97MITUpdated yesterday

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Polymarket Wallet Intelligence

An MCP server and REST API that classifies Polymarket wallets as human or bot, scores their trading edge from 0–10, and streams their current open positions. Built for AI agents on copy-trading and signal-following stacks.

# Use it from any MCP client (Claude Desktop, Cursor, etc.)

pip install polymarket-intel-mcp polymarket-intel-mcp

Or call the hosted REST API directly

curl https://polymarket-intel-production.up.railway.app/wallet/0xf1528f12e645462c344799b62b1b421a6a4c64aa

## How this fits with other Polymarket MCP servers

Status

Latest: v1.2 (May 2026) — classifier improved to distinguish active human grinders from HFT bots. See release notes and v1.3 backlog issue for what's next.

A daily snapshot job runs at 08:00 UTC and re-scores the top 50 leaderboard wallets, building a historical dataset of classification stability over time.

There are several MCP servers covering Polymarket, each at a different layer:

Server	What it does	When to use it
polymarket-intel (this)	Wallet intelligence — classify human vs bot, score trading edge, read open positions	Deciding whose signals to follow
graph-polymarket-mcp	Market data via The Graph subgraphs (20 tools, 8 subgraphs)	Reading raw on-chain market data
whitmorelabs/polymarket-mcp	Slippage, liquidity, arbitrage, price feeds	Pricing your own trades
joinQuantish/polymarket	Self-hosted trading agent	Running an autonomous bot

These complement each other. A copy-trading agent would use polymarket-intel to filter wallets worth following, then graph-polymarket-mcp to read the markets those wallets are betting on, then whitmorelabs/polymarket-mcp to size its own entries.

What it answers

"Is this trader a human or a bot?" — score_polymarket_wallet(wallet_address) → returns classification ∈ {human, bot, insufficient_data} plus a confidence score and reason codes.
"Do they actually have an edge?" — edge_score from 0–10, gated on net realised PnL so distributed-but-losing wallets don't get false positives.
"What are they betting on right now?" — get_open_positions(wallet_address) returns live positions sorted by size, refreshed every 30s.
"How has their edge changed over time?" — /wallet/{address}/history returns the score time series from the daily snapshots.

Why this exists

The Polymarket leaderboard is misleading. It includes unrealised PnL marked-to-current-price, so the names at the top are dominated by bots running structural arb plus a few wallets sitting on huge open positions that may never resolve in their favour. Agents that copy-trade naively from the leaderboard get burned.

This service runs every leaderboard wallet through behavioural fingerprinting (focus ratio, holding period, timing regularity, category concentration) plus PnL reconstruction from raw activity, and only surfaces traders that look like genuine humans with a real edge.

The dataset grows more valuable over time — every day the snapshot job runs, historical signals accumulate. Wallets that have been consistently above edge 7 for 90 days are a stronger signal than any single point-in-time score.

Distributed as both a REST API and an MCP server

Surface	Use case	Setup
MCP server	Agent that needs tool-style access	`pip install polymarket-intel-mcp`
REST API	Custom HTTP integration, dashboards	`curl https://polymarket-intel-production.up.railway.app/...`
Hosted MCP	Agent on any MCP-compatible client	Add `https://polymarket-intel-production.up.railway.app/mcp` to client config

Architecture

┌──────────────────────────────────────────────┐

│ core/ │ │ client.py — Polymarket data API client │ │ signals.py — pure signal calculators │ │ scorer.py — classifier + edge score │ │ models.py — Pydantic response schemas │ ├──────────────────────────────────────────────┤ │ db/ │ │ schema.sql — Postgres tables + indexes │ │ repository.py — Repository protocol + │ │ InMemoryRepository │ │ supabase_repo.py — Supabase impl │ │ converters.py — ScoreResult ↔ records │ ├──────────────────────────────────────────────┤ │ api/main.py — FastAPI HTTP server │ │ mcp_server/ — MCP server (stdio) │ │ scripts/ │ │ analyze_wallet.py — CLI │ │ snapshot_job.py — daily cron entry │ │ tests/ │ └──────────────────────────────────────────────┘

Core has no idea persistence exists. The API and snapshot job depend on the Repository protocol — Supabase in production, in-memory in tests and when env vars are unset. This is what makes the suite run without a database and what lets you swap Supabase for Neon, RDS, or anything else later by adding one file.

Quickstart

git clone <repo> && cd polymarket-intel

python -m venv .venv && source .venv/bin/activate pip install -r requirements-dev.txt pytest # 19 tests, all green

CLI

python scripts/analyze_wallet.py phonesculptor

python scripts/analyze_wallet.py 0xf1528f12e645462c344799b62b1b421a6a4c64aa --json

REST API

uvicorn api.main:app --reload --port 8000

open http://localhost:8000/docs

The API is split into a slow tier (cached aggressively, cheap, ideal for one-off discovery) and a fast tier (short cache, ideal for live copy-trading agents). The split exists because the underlying data has different freshness needs — a wallet's classification doesn't change minute-to-minute, but their open positions do.

Tier	Method	Path	TTL	Notes
slow	GET	`/wallet/{address}`	1h	Score blob — classification, edge_score, signals. No positions. Persisted to history (debounced).
fast	GET	`/wallet/{address}/positions`	30s	Open positions only. No DB write per call.
—	GET	`/wallet/{address}/history`	DB	Score time series
—	GET	`/wallet/{address}/positions/history`	DB	Position changes over time
—	GET	`/wallet/by-username/{username}`	1h	Convenience lookup
—	GET	`/leaderboard?limit=50`	30m	Raw Polymarket top traders
—	GET	`/leaderboard/verified?min_edge=5`	1h	Filtered to scored humans
—	GET	`/leaderboard/historical?date=…`	DB	Leaderboard at any past date
—	GET	`/snapshots/latest`	DB	When did the cron last run?

Why 30s on positions and not faster? Polygon block time is ~2s and Polymarket's activity index lags a few seconds. Polling below 10s gets you no fresher data, just rate-limit errors. 30s is the sweet spot for cost/freshness/upstream-friendliness.

Why debounced DB writes? A trading agent may hit /wallet/{address} thousands of times an hour. Writing a row per call would bloat history with near-duplicate snapshots. The score endpoint persists at most once per wallet per hour. The daily snapshot job guarantees coverage of the top 50 regardless of API traffic.

MCP server (Claude Desktop, Cursor, Continue)

python mcp_server/server.py

Then drop mcp_server/claude_desktop_config.example.json into your Claude Desktop config and edit the absolute path.

The server exposes four tools:

score_polymarket_wallet(wallet_address) — full score
score_polymarket_user(username) — lookup by display name
get_polymarket_leaderboard(limit) — raw leaderboard
get_open_positions(wallet_address) — fast snapshot of live bets

Scoring methodology

Bot triggers (any one fires → bot)

Signal	Threshold	Source
Focus ratio	> 12	Hubble Research, validated empirically
Median hold time	< 60s	HFT / MEV pattern
Timing CV	< 0.3 (n≥100)	Scheduled trading

Soft signals stack: crypto-market-maker pattern, > 200 trades/day, etc.

Edge score (0–10) for humans

Hard gate: net realised PnL ≤ 0  →  capped at 2.0

Hard gate: < 10 winning markets → capped at 3.0

35% PnL magnitude (log-scaled) 25% win rate (capped at 70%) 15% PnL distribution (penalises top-1 concentration) 15% sample size (winning markets, capped at 50) 10% win/loss ratio (capped at 3x)

Net PnL is the hard gate so wallets like neutralwave23 — many distributed tiny wins masking $375k of losses — are correctly flagged as poor.

PnL reconstruction

money_in   = sum(BUY usdcSize per conditionId)

money_out = sum(SELL usdcSize) + sum(REDEEM usdcSize) pnl = money_out - money_in

status: REDEEM exists → won SELL exists, no REDEEM → exited no SELL, no REDEEM, last trade > 7 days old → lost no SELL, no REDEEM, last trade within 7 days → open

Why activity rather than the positions endpoint: positions vanish from the API after redeem, so any naive analysis using /positions undercounts wins. Always reconstruct from /activity?type=TRADE + /activity?type=REDEEM (separate calls — comma-joined types return 400).

Persistence (Supabase)

The historical dataset is the moat. Every day the snapshot job pulls the leaderboard, scores the top N wallets, and persists three things: the score itself (wallet_scores), the wallet's open positions at that moment (open_position_snapshots), and the leaderboard as it stood (leaderboard_snapshots). After 90 days you can answer questions no one else can: "who has been consistently above edge 7 for the last quarter?", "which wallets just entered the top 50?", "show me everyone who held YES on this market three days before resolution."

Setup

# 1. Create a Supabase project, get the URL and service_role key

cp .env.example .env # fill in SUPABASE_URL and SUPABASE_KEY

2. Apply the schema (Supabase dashboard → SQL editor → paste db/schema.sql → run)

Or via psql:

psql "$DATABASE_URL" -f db/schema.sql

3. Run the snapshot job once to verify it writes:

python scripts/snapshot_job.py --top 10

If SUPABASE_URL and SUPABASE_KEY are unset, both the API and the snapshot job fall back to an in-memory repository — the suite still passes, the API still serves live scoring, but history endpoints will be empty until you wire up Supabase.

Daily snapshot job

Schedule python scripts/snapshot_job.py --top 50 daily (Railway cron, GitHub Actions, or Supabase pg_cron triggering an edge function — your call). The job is idempotent: running twice creates two snapshots, which is fine — history queries pick the closest one.

python scripts/snapshot_job.py --top 50              # production

python scripts/snapshot_job.py --top 5 --dry-run # local testing, no writes

Each run records an audit row in snapshot_runs with start/finish times, wallets scored, and error count.

Schema

Only the beginning is shown; read the rest in the repo

Polymarket Wallet Intelligence

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Accounting, finance & taxi

Common questions

Alternatives

Finance Toolkit

SolidInvoice

Korea Tax Calculator

README from the maker

Polymarket Wallet Intelligence

Or call the hosted REST API directly

Status

What it answers

Why this exists

Distributed as both a REST API and an MCP server

Architecture

Quickstart

CLI

REST API

MCP server (Claude Desktop, Cursor, Continue)

Scoring methodology

Bot triggers (any one fires → bot)

Edge score (0–10) for humans

PnL reconstruction

Persistence (Supabase)

Setup

2. Apply the schema (Supabase dashboard → SQL editor → paste db/schema.sql → run)

Or via psql:

psql "$DATABASE_URL" -f db/schema.sql

3. Run the snapshot job once to verify it writes:

Daily snapshot job

Schema