Polymarket Scan API
https://polymarket-scan-api.tatsu77.workers.dev/mcp
● degraded
x402 service listed on awesome-x402: Polymarket Scan API [x402: $0.001/call on eip155:8453, category=utility]
Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2025-06-18
negotiated, not declared
MCP readiness
F · 30/100
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here E, 18.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 0/10 | initialize did not answer cleanly (HTTP 404). |
| Live MCP endpoint | 5/25 | Endpoint answers, but not with MCP JSON-RPC (60 ms). |
| Protocol revision | 6/10 | Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 2.05/15 | 3/22 probes succeeded over 30 days (14%). |
| Tool declaration | 5/10 | Lists 2 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 0/5 | How to authenticate is not stated. |
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive
(60 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.
Compared with peers
Against 53,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.
- Readiness
- Higher than 2% of peers
- This listing 30 · peer median 81
- Latency
- Faster than 96% of peers
- This listing 60 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Live MCP endpoint −20
— Answer initialize and tools/list at the declared endpoint.
Now: Endpoint answers, but not with MCP JSON-RPC (60 ms).
- Uptime (30 days) −12.9
— Stay reachable in our daily probes.
Now: 3/22 probes succeeded over 30 days (14%).
- Valid MCP handshake −10
— Complete the MCP handshake without errors.
Now: initialize did not answer cleanly (HTTP 404).
Listed in
Directories this entry was found in.
How to connect
MCP endpoint (streamable-http)
https://polymarket-scan-api.tatsu77.workers.dev/mcpJSON-RPC initialize probe
curl -X POST https://polymarket-scan-api.tatsu77.workers.dev/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'Listed at (agenstry)
https://agenstry.com/mcp/x402/polymarket-scan-api