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

weather-of-record

https://weatherofrecord.com

Registry code: dc81082ba158126c

api record

Weather of Record returns published weather records for a U.S. street address and date. Records reach back to about 1960. A lookup takes about two minutes: call submit_lookup, then call get_lookup with its lookup_id until the status is done or failed. These are records, not opinions: nothing returned is a determination about any property. The absence of a record is not evidence that an event did not occur. Running a lookup needs a free key (10 lookups a month) from https://weatherofrecord.com/api, sent as an Authorization: Bearer header. get_county_storm_history needs no key: it returns the…

endpoint
https://weatherofrecord.com/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 weather-of-record live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is weather-of-record free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does weather-of-record have?
4 tools: submit_lookup, get_forecast, get_county_storm_history, get_lookup.
Is weather-of-record 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
98.6%

90 days 98.8%· all time 98.8%

latency
318ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 427 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • look up historical weather records for an address and date
  • check status of a weather lookup
takes → gives
text, data → data
tools
1 reads1 changes data
_ 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 4 tools
1 auth-required 3 never probed 1 of 4 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.

  • get_lookup reads auth-required 24h ago

    Check a lookup started with submit_lookup. The status is queued, running, done or failed. When done, the result holds the records with their provenance and a notice. A failed lookup carries a reason and no records. The absence of a record is not evidence that an event did not occur. Results are kept for 30 days.

    mcp-tool

    {
      "type": "object",
      "required": [
        "lookup_id"
      ],
      "properties": {
        "lookup_id": {
          "type": "string",
          "description": "The lookup_id from submit_lookup"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • submit_lookup changes data unknown never probed

    Start a weather-records lookup for one U.S. street address and date. Returns a lookup_id; the records are ready in about two minutes -- call get_lookup with it. Records reach back to about 1960. Records, not opinions: nothing returned is a determination about any property. Each accepted lookup uses one of the key's 10 free lookups this month.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address",
        "date"
      ],
      "properties": {
        "date": {
          "type": "string",
          "format": "date",
          "description": "The date of interest, YYYY-MM-DD"
        },
        "address": {
          "type": "string",
          "description": "Full U.S. street address with city, state and ZIP, e.g. 123 Main St, Nashville, TN 37203"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • get_forecast unknown 24h ago

    Returns the current National Weather Service forecast for a US point. This is a forecast, not a record of observed weather. Send latitude and longitude (no key needed), or a U.S. street address (needs the free key). Returns 12-hour periods for about seven days and hourly values, with issued_utc, the time the National Weather Service issued it, and a stale flag. U.S. coverage only.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "hours": {
          "type": "integer",
          "default": 48,
          "maximum": 168,
          "minimum": 1,
          "description": "Hourly values to return"
        },
        "address": {
          "type": "string",
          "description": "Full U.S. street address with city, state and ZIP (needs the free key)"
        },
        "periods": {
          "type": "integer",
          "default": 14,
          "maximum": 14,
          "minimum": 1,
          "description": "12-hour periods to return"
        },
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • get_county_storm_history unknown 24h ago

    Returns the hail, thunderstorm wind and tornado events of record for one published U.S. county over about the last three years, from NOAA's Storm Events Database, with the source file and revision named. Needs no key. state is the two-letter abbreviation and county is written as in the county page address, for example tn and sumner. The list of published counties is at https://weatherofrecord.com/api/v1/storms. County level only, never a street address. The absence of a record is not evidence that an event did not occur.

    mcp-tool

    {
      "type": "object",
      "required": [
        "state",
        "county"
      ],
      "properties": {
        "state": {
          "type": "string",
          "pattern": "^[A-Za-z]{2}$",
          "description": "Two-letter state abbreviation, e.g. tn"
        },
        "county": {
          "type": "string",
          "description": "County as in the page address, e.g. sumner or virginia-beach-city"
        }
      },
      "additionalProperties": false
    }
    arguments 19 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 dc81082ba158126c.

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

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.