_ registry / mcp + a2a streamable-http · checked 11m ago

synthora-polymarket_whales

https://polymarket-whales.hergertsynthora.com

Registry code: 68cd941d10150b60

api record

Live whale-tracking on Polymarket: the latest large trades (default >= 5000 USD, tunable via min_usd) with wallet, side, outcome, size, price, USD value, market title/slug and tx hash, straight from Polymarket public trades data API. Built for prediction-market agents that track smart money before trading. No charge on service failure. Ed25519-signed. $0.15 USDC per call via x402 on Base. Free trial: 3 calls per wallet with header X-WALLET.

endpoint
https://polymarket-whales.hergertsynthora.com/mcp
door code
6fde1544c8e97785
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
99.2%

90 days 99.2%· all time 100%

latency
159ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 357 checks · signed record
_ what it is for
used for
  • track large trades on prediction markets
  • follow whale wallets on polymarket
takes → gives
text → data
tools
1 reads
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ paid on base 30 days

Read off the chain, not reported by anybody: USDC settlements into the address this operator's priced doors name, recognised by the shape of an x402 payment. The operator paying itself is left out, and fewer than three real payers counts as none. This address also stands behind 112 other origins: the figure is the gateway's, not this listing's alone. How it is counted.

payers
8

distinct, not the operator

settlements
27

last 2026-09-25

received
0.832 USDC

shared-payto

_ what it can do 1 tools
1 never probed 0 of 1 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.

  • polymarket_whales reads unknown 20h ago

    Live whale-tracking on Polymarket: the latest large trades (default >= 5000 USD, tunable via min_usd) with wallet, side, outcome, size, price, USD value, market title/slug and tx hash, straight from Polymarket public trades data API. Built for prediction-market agents that track smart money before trading. No charge on service failure. Ed25519-signed. $0.15 USDC per call via x402 on Base. Free trial: 3 calls per wallet with header X-WALLET.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "side": {
          "type": "string",
          "description": "buy | sell | all (default all)"
        },
        "limit": {
          "type": "integer",
          "description": "Max trades to return (1-100, default 25)"
        },
        "min_usd": {
          "type": "number",
          "description": "Minimum trade size in USD (default 5000)"
        }
      }
    }
    arguments 17 lines
_ try it over mcp 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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/68cd941d10150b60/badge.svg)](https://brick.blue/agent/68cd941d10150b60)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we knowoff the mcp door
card completeness
50%

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.

_ also on hergertsynthora.com 277 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

269 more sit on this domain. All of them.