CrowdIntel — Polymarket Wallet Intelligence
Polymarket wallet intelligence for AI agents: scored wallets, insider signals, whale flow.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http crowdintel-polymarket-wallet-intelligenc 'https://mcp.crowdintel.xyz/mcp'
{
"mcpServers": {
"crowdintel-polymarket-wallet-intelligenc": {
"type": "http",
"url": "https://mcp.crowdintel.xyz/mcp"
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
Polymarket Agent Kit
Ask any Polymarket wallet, market, or funding cluster a question from your agent — resolved PnL, shrinkage-adjusted win rate, insider score, cluster membership, and trade history, over 1.88B indexed on-chain fills. Delivered through MCP or REST.
Not a price feed and not a trading bot: CrowdIntel answers who is on the other side and is their edge real. Use it for the decision, then execute through Polymarket's official CLOB API.
The official Polymarket/agents repo (3.7K★) was archived in May 2026 and no longer runs. This kit is a maintained, intelligence-first path for the same builders: connect your agent to the CrowdIntel MCP server for the decision side, and pair it with the official CLOB client for execution.
Read-only by design. No custody, no order placement, no keys to your funds. Your agent decides with CrowdIntel data; it trades through Polymarket's official CLOB API. Not affiliated with Polymarket — see DISCLAIMER.
60-second quickstart (Claude Desktop)
- Sign in at crowdintel.xyz → Settings → API → mint an MCP token (
cint_mcp_…). Free on every plan, no credit card. - Add to your
claude_desktop_config.json:
{
"mcpServers": {
"crowdintel": {
"type": "http",
"url": "https://mcp.crowdintel.xyz/mcp",
"headers": {
"Authorization": "Bearer cint_mcp_YOUR_TOKEN_HERE"
}
}
}
}
- Restart Claude Desktop. Ask: "Which Polymarket wallets have real category edge in politics right now?"
Cursor, Zed, and raw JSON-RPC setups: quickstart/. Every endpoint also exists as plain REST — see the API reference and the drop-in AI context doc.
What your agent gets
| Group | Tools |
|---|---|
| Wallets | get_wallet_stats (flagship dossier), get_wallet_timing (entry-timing edge), get_wallet_alerts (insider scores), search_wallets |
| Markets | get_market, get_market_alerts, get_market_flow (smart-money vs crowd), get_market_movers, get_whale_activity |
| Clusters | get_cluster, find_funding_clusters |
| Alpha discovery | scan_insider_signals, screen_wallets_by_edge |
| Cohorts | list_cohorts, get_cohort |
| Investigations | get_investigation, list_investigations |
| Leaderboard | get_leaderboard |
Full parameter reference: docs/tools.md.
Recipes — agent patterns that work
- Follow the smart money on a hot market —
get_market_movers→get_market_flow→get_whale_activity. - Should my agent trust this wallet's signal? —
search_wallets→get_wallet_stats+get_wallet_timing+get_wallet_alerts. Raw win rates lie (small samples, wash trading, sybil clusters); the dossier ships shrinkage-adjusted stats. - Find a coordinated ring before it resolves —
scan_insider_signals/find_funding_clusters→get_cluster. - Category-specialist copy-trade screen —
screen_wallets_by_edge→get_leaderboard.
Each recipe ends where execution begins: hand the decision to the official CLOB client. This kit never places orders.
Agent Skills
Four drop-in skills for Claude / Cursor / any Agent-Skills client — each one is a procedure, not a prompt, and each states where its numbers come from:
| Skill | Use it to |
|---|---|
polymarket-wallet-intel | Vet a wallet before copying or fading it |
polymarket-whale-flow | Read smart-money vs crowd flow on a live market |
polymarket-sybil-clusters | Tell a coordinated ring from shared infrastructure |
polymarket-backtest | Replay a detector over resolved markets before risking money |
Copy skills/ into ~/.claude/skills/ (or your client's skills directory).
Rate limits
Every tool answers on a free token; paid tiers raise the caps (see pricing). MCP daily calls: 20 free / 50 Pro / 300 Terminal / 1,500 Terminal Pro. REST: 50 req/hr free up to 5,000 req/hr Terminal Pro.
Links
- MCP server guide · API reference · OpenAPI 3.1 spec
- AI context doc — one file that teaches any LLM the whole API
- Methodology — how scores and stats are computed
Docs
- docs/metrics.md — the formulas: EV-per-dollar CI, event-clustered z, FDR q-values, the gated insider score.
- docs/pitfalls.md — seven ways Polymarket wallet data lies to you. Win rate can filter a board; it can never sort one.
- docs/comparison.md — honest comparison, including when to use the official CLOB, a raw dataset, or Bitquery instead.
- docs/tools.md — every tool, by group.
- examples/ — Python screener, TypeScript webhook receiver, MCP config.
- openapi.json — the full REST spec (40 endpoints), refreshed weekly by CI.
Last updated: 2026-08-16 · 1.88B fills · 2.13M markets · 3.06M scored wallets (freshness).
License
MIT. Not affiliated with, endorsed by, or sponsored by Polymarket — see DISCLAIMER.
Frequently asked questions
What is CrowdIntel — Polymarket Wallet Intelligence?
Polymarket wallet intelligence for AI agents: scored wallets, insider signals, whale flow.
How do I install CrowdIntel — Polymarket Wallet Intelligence?
It runs as a remote server. In Claude Code: claude mcp add --transport http crowdintel-polymarket-wallet-intelligenc 'https://mcp.crowdintel.xyz/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does CrowdIntel — Polymarket Wallet Intelligence need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is CrowdIntel — Polymarket Wallet Intelligence open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains CrowdIntel — Polymarket Wallet Intelligence?
It is published by crowdintel-xyz. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.