Connect Vertical Weather and your agent gets 3 tools, among them get_atmospheric_profile, get_capabilities, get_usage. It answers at https://api.verticalweather.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 26 September 2026; the last check, on 9 November 2026, succeeded.
Wind, temperature, pressure, humidity and air density at chosen heights, from NOAA GFS.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_atmospheric_profile | 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 Inputs: latitude, longitude, time, altitudes_m, altitude_reference, ground_elevation_m_msl |
get_capabilities | Current coverage (time range, heights, fields) and usage limits. No API key needed. |
get_usage | Today's data-fetch count and remaining daily allowance for the caller's account (UTC day). |
Every block below points at https://api.verticalweather.com/mcp. Pick your client and copy.
claude mcp add --transport http vertical-weather https://api.verticalweather.com/mcp
{
"mcpServers": {
"vertical-weather": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.verticalweather.com/mcp"]
}
}
}{
"mcpServers": {
"vertical-weather": {
"url": "https://api.verticalweather.com/mcp"
}
}
}{
"servers": {
"vertical-weather": {
"type": "http",
"url": "https://api.verticalweather.com/mcp"
}
}
}{
"context_servers": {
"vertical-weather": {
"url": "https://api.verticalweather.com/mcp"
}
}
}{
"mcpServers": {
"vertical-weather": {
"serverUrl": "https://api.verticalweather.com/mcp"
}
}
}{
"mcpServers": {
"vertical-weather": {
"url": "https://api.verticalweather.com/mcp"
}
}
}name: Vertical Weather
version: 0.0.1
schema: v1
mcpServers:
- name: Vertical Weather
type: streamable-http
url: https://api.verticalweather.com/mcp{
"mcpServers": {
"vertical-weather": {
"httpUrl": "https://api.verticalweather.com/mcp"
}
}
}{
"mcpServers": {
"vertical-weather": {
"type": "http",
"url": "https://api.verticalweather.com/mcp"
}
}
}{
"mcpServers": {
"vertical-weather": {
"url": "https://api.verticalweather.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.verticalweather.com%2Fmcp&type=streamable_http&id=vertical-weather&name=Vertical%20Weather
It answered our last check on 9 November 2026 in 183 ms. Over 4 checks since 26 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by verticalweather.com and served from api.verticalweather.com, the vendor's own domain: https://api.verticalweather.com/mcp.
3, as returned by the server's own tools/list on 16 November 2026: get_atmospheric_profile, get_capabilities, get_usage.
It answered our last check on 9 November 2026 in 183 ms. Over 4 checks since 26 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.verticalweather.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.verticalweather. Endpoint host: api.verticalweather.com. ARD identifier: urn:air:com.verticalweather:mcp:vertical-weather.
First indexed 26 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.