Vertical Weather
https://api.verticalweather.com
Registry code: d71dfd739d5f34ad
Vertical Weather returns the atmosphere above a point at a given time: wind,
temperature, pressure, humidity and air density at heights you choose, from
- endpoint
- https://api.verticalweather.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 Vertical Weather live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is Vertical Weather free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does Vertical Weather have?
- 3 tools: get_atmospheric_profile, get_capabilities, get_usage.
- Is Vertical Weather 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.
90 days 99.7%· all time 99.7%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- get atmospheric profile
- get wind data
- get temperature data
- get pressure data
- get humidity data
- takes → gives
- data → data
- tools
- 3 reads
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.
through this hub
successful
what callers paid
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_capabilities reads open 11h ago
Current coverage (time range, heights, fields) and usage limits. No API key needed.
{ "type": "object", "title": "get_capabilitiesArguments", "properties": {} }arguments 5 linesget_usage reads auth-required 11h ago
Today's data-fetch count and remaining daily allowance for the caller's account (UTC day).
{ "type": "object", "title": "get_usageArguments", "properties": {} }arguments 5 linesget_atmospheric_profile reads unknown 11h ago
Wind, temperature, pressure, humidity and air density at chosen heights above a point. Each level has wind_u_ms (towards east), wind_v_ms (towards north), wind_speed_ms, wind_direction_deg (where the wind comes FROM, clockwise from north; 0 at zero speed means calm), temperature_k, pressure_pa, specific_humidity_kg_kg, relative_humidity_pct and density_kg_m3. valid_time is the model time actually used; provenance names the GFS run and grid point. Heights outside the model column are refused with the range that is available.
{ "type": "object", "title": "get_atmospheric_profileArguments", "required": [ "latitude", "longitude", "time", "altitudes_m", "altitude_reference" ], "properties": { "time": { "type": "string", "title": "Time", "description": "ISO 8601 timestamp with a timezone, e.g. 2026-10-03T18:00:00Z. Up to 14 days ahead or about ten days back." }, "latitude": { "type": "number", "title": "Latitude", "maximum": 90, "minimum": -90, "description": "Decimal degrees, north positive." }, "longitude": { "type": "number", "title": "Longitude", "maximum": 180, "minimum": -180, "description": "Decimal degrees, east positive." }, "altitudes_m": { "type": "array", "items": { "type": "number" }, "title": "Altitudes M", "maxItems": 32, "minItems": 1, "description": "1 to 32 different heights in metres." }, "altitude_reference": { "enum": [ "agl", "msl" ], "type": "string", "title": "Altitude Reference", "description": "agl: heights above ground level. msl: heights above mean sea level." }, "ground_elevation_m_msl": { "anyOf": [ { "type": "number", "maximum": 10000, "minimum": -1000 }, { "type": "null" } ], "title": "Ground Elevation M Msl", "default": null, "description": "Optional site elevation in metres above sea level, used for agl heights instead of the model's terrain." } } }arguments 66 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idd71dfd739d5f34ad.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/d71dfd739d5f34ad/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/d71dfd739d5f34ad?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.