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

Weather for prediction-market agents (Kalshi & Polymarket temperature markets)

https://weather-x402.linholiday.workers.dev

Registry code: be4d5c0eee4aef2c

api record

Paid tools use x402 on eip155:8453 to 0xA94AaF06ad79baD31E0DF25187d376780a8836c6. On tools/call without payment, the tool result is isError with PaymentRequired (structuredContent + content[0].text). Retry with params._meta['x402/payment'] set to a PaymentPayload.

endpoint
https://weather-x402.linholiday.workers.dev/mcp
protocol
streamable-http ·2025-03-26
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 Weather for prediction-market agents (Kalshi & Polymarket temperature markets) live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Weather for prediction-market agents (Kalshi & Polymarket temperature markets) free to use?
Not measured yet.
What tools does Weather for prediction-market agents (Kalshi & Polymarket temperature markets) have?
5 tools: ping, observed, forecast, settlement, market_station.
Is Weather for prediction-market agents (Kalshi & Polymarket temperature markets) 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
167ms

last good check

priced tools
4

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 4 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
4

distinct

settlements
12

last 2026-11-03

received on chain
0.13 USDC

concentrated, shared-payto

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

  • observed 0.01 USDC paid never probed

    Observed max/min so far today at a settlement station from METAR/SPECI reports (incl. 6/24-hour max/min groups), local-day aware: separate Kalshi climate-day (LST) and Polymarket local-day windows, plus latest reading. Price: 0.01 USDC via x402 on eip155:8453.

    mcp-tool

    {
      "type": "object",
      "required": [
        "station"
      ],
      "properties": {
        "preview": {
          "type": "boolean"
        },
        "station": {
          "type": "string",
          "description": "Settlement station ICAO id, e.g. KMDW, KLGA, EGLC"
        }
      }
    }
    arguments 15 lines
  • forecast 0.02 USDC paid never probed

    Daily high/low forecast for a prediction-market settlement station and date: NWS gridpoint forecast + MET Norway, per-source values, consensus and spread, in F and C, on the exact settlement day window (Kalshi local-standard-time climate day or Polymarket local day). Price: 0.02 USDC via x402 on eip155:8453.

    mcp-tool

    {
      "type": "object",
      "required": [
        "station"
      ],
      "properties": {
        "date": {
          "type": "string",
          "description": "YYYY-MM-DD in the station's local time; today to +9 days (default today)"
        },
        "market": {
          "enum": [
            "kalshi",
            "polymarket"
          ],
          "type": "string",
          "description": "Which settlement day to use (default: kalshi if the station has a Kalshi market)"
        },
        "preview": {
          "type": "boolean",
          "description": "If true and supported, return fixed free sample"
        },
        "station": {
          "type": "string",
          "description": "Settlement station ICAO id, e.g. KNYC (Kalshi NYC), KLGA (Polymarket NYC), EGLC (Polymarket London). See /stations"
        }
      }
    }
    arguments 28 lines
  • settlement 0.01 USDC paid never probed

    Settlement value for a past day: the official NWS Daily Climate Report (CLI) high/low that Kalshi settles on (first non-preliminary report, with preliminary and later corrections), and the Polymarket-style max/min from the station's hourly readings. Price: 0.01 USDC via x402 on eip155:8453.

    mcp-tool

    {
      "type": "object",
      "required": [
        "station"
      ],
      "properties": {
        "date": {
          "type": "string",
          "description": "YYYY-MM-DD (station local); yesterday by default, up to 6 days back"
        },
        "preview": {
          "type": "boolean"
        },
        "station": {
          "type": "string",
          "description": "Settlement station ICAO id"
        }
      }
    }
    arguments 19 lines
  • market_station 0.01 USDC paid never probed

    Resolve a Kalshi ticker, Polymarket event slug/URL or city to the exact settlement station, climate report code, day window, units, strike bracket and the station-trap warning when Kalshi and Polymarket use different stations. Price: 0.01 USDC via x402 on eip155:8453.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "Kalshi ticker/series (KXHIGHNY, KXHIGHNY-26OCT21-B88.5), Polymarket event slug or URL (highest-temperature-in-nyc-on-october-21-2026), city name, or ICAO"
        },
        "venue": {
          "enum": [
            "kalshi",
            "polymarket"
          ],
          "type": "string",
          "description": "Filter for city-name queries"
        },
        "preview": {
          "type": "boolean"
        }
      }
    }
    arguments 23 lines
  • ping unknown never probed

    Free health check

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 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 be4d5c0eee4aef2c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/be4d5c0eee4aef2c/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/be4d5c0eee4aef2c/badge.svg)](https://brick.blue/agent/be4d5c0eee4aef2c?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
90%

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.