_ registry / mcp streamable-http · checked 16h ago

Polymarket Scan API

https://polymarket-scan-api.tatsu77.workers.dev

Registry code: c739c387db0053e4

api record

x402 service listed on awesome-x402: Polymarket Scan API [x402: $0.001/call on eip155:8453, category=utility]

from a public catalogue that lists it, not from the operator

endpoint
https://polymarket-scan-api.tatsu77.workers.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Polymarket Scan API live?
Yes — it answered the hub's last check (checked 16h ago). It answered 100% of checks over the last 30 days.
Is Polymarket Scan API free to use?
Not measured yet.
What tools does Polymarket Scan API have?
2 tools: scan_liquidity_anomaly, scan_history.
Is Polymarket Scan API safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
127ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 258 checks · signed record
  • degraded → live
_ what it is for
used for
  • scan polymarket for liquidity anomalies
  • view liquidity scan history
takes → gives
text → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • scan_liquidity_anomaly reads unknown never probed

    Scan all active Polymarket prediction markets for liquidity anomalies — thin books, depth surges, and mean-reversion setups. Returns scored opportunities with trade recommendations (AVOID_ENTRY / MONITOR / CONSIDER_ENTRY) and urgency levels. Paid tool: $0.018 USDC per call via x402 (payment handled in-protocol; x402-aware MCP clients pay automatically).

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Number of opportunities to return (1–20, default 10)."
        },
        "direction": {
          "enum": [
            "thin",
            "surge",
            "both"
          ],
          "type": "string",
          "description": "Filter by anomaly type: 'thin' (thin books), 'surge' (depth surges), or 'both' (all types)."
        },
        "min_score": {
          "type": "number",
          "maximum": 1,
          "minimum": 0,
          "description": "Minimum opportunity score (0–1, default 0.7). Use 0.8 for high-confidence signals only."
        }
      }
    }
    arguments 27 lines
  • scan_history reads unknown never probed

    Time-series history of Polymarket liquidity scan snapshots (up to 24h, one snapshot per minute). Useful for spotting liquidity trends and verifying how long an anomaly has persisted. Paid tool: $0.005 USDC per call via x402 (payment handled in-protocol; x402-aware MCP clients pay automatically).

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "hours": {
          "type": "integer",
          "maximum": 24,
          "minimum": 1,
          "description": "Hours of history to fetch (1–24, default 1)."
        },
        "limit": {
          "type": "integer",
          "maximum": 60,
          "minimum": 1,
          "description": "Maximum number of snapshots to return (1–60, default 10)."
        },
        "min_score": {
          "type": "number",
          "maximum": 1,
          "minimum": 0,
          "description": "Minimum opportunity score filter per snapshot (0–1, default 0)."
        }
      }
    }
    arguments 24 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c739c387db0053e4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c739c387db0053e4/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c739c387db0053e4/badge.svg)](https://brick.blue/agent/c739c387db0053e4?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.