Polymarket Trader MCP Server
polymarket-trader-mcp
npm
v1.6.2
Published by demwick — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 48
Each tool and what it can reach — statically extracted from the published source.
analysis.price_historyingests untrusted inputmarkets.priceingests untrusted inputtraders.discoveringests untrusted inputanalysis.arbitrageno sensitive capabilityanalysis.compareno sensitive capabilityanalysis.flowno sensitive capabilityanalysis.holdersno sensitive capabilityanalysis.opportunityno sensitive capabilityanalysis.qualityno sensitive capabilityconfig.dashboardno sensitive capability
Show 38 more tools ↓
config.go_liveno sensitive capabilityconfig.historyno sensitive capabilityconfig.log_cycleno sensitive capabilityconfig.safety_limitsno sensitive capabilityconfig.setno sensitive capabilitymarkets.discoverno sensitive capabilitymarkets.eventsno sensitive capabilitymarkets.featuredno sensitive capabilitymarkets.relatedno sensitive capabilitymarkets.searchno sensitive capabilitymarkets.trendingno sensitive capabilitymarkets.watchno sensitive capabilitymarkets.watch_priceno sensitive capabilitymonitor.startno sensitive capabilitymonitor.stopno sensitive capabilityorders.batchno sensitive capabilityorders.buyno sensitive capabilityorders.cancelno sensitive capabilityorders.listno sensitive capabilityorders.sellno sensitive capabilityorders.statusno sensitive capabilityportfolio.balanceno sensitive capabilityportfolio.getno sensitive capabilityportfolio.optimizeno sensitive capabilityportfolio.riskno sensitive capabilitypositions.check_exitsno sensitive capabilitypositions.closeno sensitive capabilitypositions.listno sensitive capabilitypositions.set_exit_rulesno sensitive capabilitytraders.analyzeno sensitive capabilitytraders.backtestno sensitive capabilitytraders.positionsno sensitive capabilitytraders.scoreno sensitive capabilitywatchlist.addno sensitive capabilitywatchlist.listno sensitive capabilitywatchlist.rebalanceno sensitive capabilitywta.bidno sensitive capabilitywta.discoverno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (48 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.6.2 latest |
A 96/100 | 0 | 1.9.0 | 2026-07-24 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan polymarket-trader-mcp --onlineMore in Finance & Commerce
Security scan results for the 1money MCP server.
Signed verification attestations for agent decisions: business, price, freshness, claim checks.
Security scan results for the Actual MCP server.
Security scan results for the Actual Budget MCP server.
Security scan results for the Adyen MCP server.
Trusted agent-commerce hub: discover, trust-check, and route x402 payments with failover.