MCP.Market

Polymarket Wallet Intelligence MCP server

not responding
by aemery13·io.github.aemery13/polymarket-intel·v1.0.1
No reviews yet

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

C58/100grade C
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
C58/100

full report

Adoption
New

0 stars27 downloads/wk

Reviews

Write one

Nobody has reviewed Polymarket Wallet Intelligence yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Polymarket Wallet Intelligence tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

1 high
  • Code scan23 source files scanned25/25
  • Live reliabilityremote unreachable: Streamable HTTP error: Error POSTing to endpoint: {"status":"error","code":404,"message":"Application not found","request_id":"8zI4daM0Spu9ZCiG-_9nXA"}0/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 150 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • highRemote endpoint did not respondreliability.unreachable

    Streamable HTTP error: Error POSTing to endpoint: {"status":"error","code":404,"message":"Application not found","request_id":"8zI4daM0Spu9ZCiG-_9nXA"}

Overall 58/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Polymarket Wallet Intelligence compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
58/100
higher than 13% of 48,255 servers
Uptime
0%
of our recent checks; the typical remote server answers 100%
Response time
574 ms
faster than 25% of 30,031 servers
Downloads a week
27
more than 14% of 12,191 servers with a package

Install Polymarket Wallet Intelligence in Claude Code, Cursor or VS Code

claude mcp add --transport http polymarket-intel https://polymarket-intel-production.up.railway.app/mcp
Add to Cursor

What the publisher says

From the Polymarket Wallet Intelligence repository's README, as published. We do not edit it. Read it on GitHub

Polymarket Wallet Intelligence

<!-- mcp-name: io.github.aemery13/polymarket-intel -->

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:

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?" — scorepolymarketwallet(walletaddress) → returns classification ∈ {human, bot, insufficientdata} 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?" — getopenpositions(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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-10-14downgradeB → Cscore 58: Remote endpoint did not respond

Polymarket Wallet Intelligence: common questions

Is Polymarket Wallet Intelligence MCP server safe?
With care: it is graded C, so read the findings first (58/100). Read the Polymarket Wallet Intelligence safety report
How do I install Polymarket Wallet Intelligence?
It runs remotely at polymarket-intel-production.up.railway.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Polymarket Wallet Intelligence need an API key?
Yes. The registry entry asks for POLYMARKET_INTEL_API_KEY, X-API-Key.
Is Polymarket Wallet Intelligence maintained?
The last commit was 170 days ago (2026-05-18). The latest release is v1.0.1.
Is Polymarket Wallet Intelligence up?
0% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Polymarket Wallet Intelligence compare with other MCP servers?
safety score 58/100 (higher than 13% of 48,255 servers); uptime 0% (of our recent checks; the typical remote server answers 100%); response time 574 ms (faster than 25% of 30,031 servers). Full comparison.