# Weather That Doesn't Suck (remote · weatherthatdoesntsuck.com)

Weather decisions for outdoor plans: should I go, when, what to wear, what you will meet en route.

- Trust score: 83/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `weatherthatdoesntsuck.com`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-weatherthatdoesntsuck-weather/api-mcp.md), [page](https://verifymcp.io/servers/com-weatherthatdoesntsuck-weather/api-mcp)

## Channel facts

- Endpoint: `https://weatherthatdoesntsuck.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 5071 tokens (~338/item across 15 items; 11 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Weather That Doesn't Suck MCP server?

Weather That Doesn't Suck is a hosted endpoint at https://weatherthatdoesntsuck.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-weatherthatdoesntsuck-weather 'https://weatherthatdoesntsuck.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-weatherthatdoesntsuck-weather": {
      "url": "https://weatherthatdoesntsuck.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-weatherthatdoesntsuck-weather": {
      "type": "http",
      "url": "https://weatherthatdoesntsuck.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-weatherthatdoesntsuck-weather]
url = "https://weatherthatdoesntsuck.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-weatherthatdoesntsuck-weather": {
      "type": "remote",
      "url": "https://weatherthatdoesntsuck.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-weatherthatdoesntsuck-weather --url 'https://weatherthatdoesntsuck.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-weatherthatdoesntsuck-weather:
    url: "https://weatherthatdoesntsuck.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-weatherthatdoesntsuck-weather": {
      "Transport": "http",
      "Url": "https://weatherthatdoesntsuck.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-weatherthatdoesntsuck-weather -t streamable-http -u 'https://weatherthatdoesntsuck.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-weatherthatdoesntsuck-weather": {
      "type": "http",
      "url": "https://weatherthatdoesntsuck.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 83, −1)

- [functional] Stability: pass → 0.97

### 2026-11-03 (score 84, +1)

- [security] Stability: 0.97 → pass

### 2026-11-01 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (11)

### `get_weather` (~313 tokens)

Weather now and the days ahead

Plain-language weather for a place: one sentence first, then current conditions, the next 24 hours, the next 7 days, and official alerts. Use it for "what's the weather", "do I need a jacket", "is it going to rain". For a decision about doing something outdoors (a run, a hike, staining a deck), use outdoor_activity_weather instead: it answers "should I?", not just "what is it?". `data.current` says whether it is a station observation, a model estimate, or a forecast hour. `data.alerts.status` says whether "no alerts" can be believed: only "ok" means we checked. Answers carry their sources, how old the data is, and say so when it came from cache.

Input parameters:

- `hours` (integer): Hours of hourly detail to include. Default 24.
- `latitude` (number): Latitude in degrees. Use with longitude instead of location.
- `location` (string): A place name such as "Glenbeulah, WI" or "Greenbush, Wisconsin", or coordinates as "43.79,-88.05". Add the state or country for small towns, because a bare "Greenbush" matches several places.
- `longitude` (number): Longitude in degrees, west negative. Use with latitude instead of location.
- `units` (string): imperial (F, mph, inches) or metric (C, km/h, mm). Defaults to imperial in the United States and metric elsewhere.

### `get_forecast` (~375 tokens)

Forecast for a time period

The forecast for a stretch of time: "What's Saturday looking like?", "What will conditions be between 6 PM and midnight?", "this weekend". Give start_time (and optionally end_time or duration_hours). Returns a one-line summary, the temperature range, rain, wind, any conditions worth acting on, and the hourly and daily rows. The forecast reaches about seven days. Beyond that it says so and does not guess.

Input parameters:

- `duration_hours` (number): Instead of end_time: how many hours to cover.
- `end_time` (string): When the period ends, in the same formats as start_time. "midnight" means the next midnight.
- `latitude` (number): Latitude in degrees. Use with longitude instead of location.
- `location` (string): A place name such as "Glenbeulah, WI" or "Greenbush, Wisconsin", or coordinates as "43.79,-88.05". Add the state or country for small towns, because a bare "Greenbush" matches several places.
- `longitude` (number): Longitude in degrees, west negative. Use with latitude instead of location.
- `start_time` (string): When the period starts. Defaults to now. An ISO 8601 time such as 2026-10-03T18:00:00-05:00 (read in the place's own time zone when it has no offset), or plain words: "now", "tonight", "tomorrow morn…
- `units` (string): imperial (F, mph, inches) or metric (C, km/h, mm). Defaults to imperial in the United States and metric elsewhere.

### `outdoor_activity_weather` (~549 tokens)

Should I do this outside?

Our flagship tool. Turns weather into a decision for a specific outdoor activity: a practical verdict (go, go_with_caveats, marginal, no_go), a one-sentence reason, the temperature and feels-like range, rain, wind, sunset, what to wear, and the concerns. Activities: walking, hiking, trail_running, road_running, cycling, camping, hunting, fishing, yard_work, construction, painting_finishing, general_outdoor. Give a start_time and a duration_hours, or a phrase like "tomorrow morning". If you name a whole day ("Saturday"), it finds and judges the best window inside it. It keeps the forecast apart from our advice, says what it is inferring (mud, ice, fog) and what it cannot know (the trail surface), and an official warning overrides everything. To find WHEN to go, use find_best_weather_window.

Input parameters:

- `activity` (string, required): What the person is doing. One of: walking, hiking, trail_running, road_running, cycling, camping, hunting, fishing, yard_work, construction, painting_finishing, general_outdoor. Plain words work too…
- `duration_hours` (number): How long it lasts. Defaults to the usual length for the activity, and says so.
- `intensity` (string): How hard the effort is, which changes what to wear. Defaults to the usual effort for the activity.
- `latitude` (number): Latitude in degrees. Use with longitude instead of location.
- `location` (string): A place name such as "Glenbeulah, WI" or "Greenbush, Wisconsin", or coordinates as "43.79,-88.05". Add the state or country for small towns, because a bare "Greenbush" matches several places.
- `longitude` (number): Longitude in degrees, west negative. Use with latitude instead of location.
- `start_time` (string): When it starts. Defaults to now. An ISO 8601 time such as 2026-10-03T18:00:00-05:00 (read in the place's own time zone when it has no offset), or plain words: "now", "tonight", "tomorrow morning", "S…
- `units` (string): imperial (F, mph, inches) or metric (C, km/h, mm). Defaults to imperial in the United States and metric elsewhere.

### `find_best_weather_window` (~529 tokens)

When is the best time?

Finds the best time on a day for an activity. Returns the best window, an alternate, and any clearly bad stretch, each with a short reason. Windows are stretches, not exact hours: when several start times are about equally good they are reported as one stretch, and when the whole day is about the same it says so. Use it for "when should I go?", "what's the best time Saturday?", "Kilian and I want to hike Saturday". Give a date such as "Saturday", "tomorrow" or 2026-10-03. If nothing on the day is good it says so and names the least bad stretch.

Input parameters:

- `activity` (string, required): What the person is doing. One of: walking, hiking, trail_running, road_running, cycling, camping, hunting, fishing, yard_work, construction, painting_finishing, general_outdoor. Plain words work too…
- `date` (string): The day to search. Defaults to today. A part of a day ("tomorrow morning") narrows the search to it, and "this weekend" compares both days. An ISO 8601 time such as 2026-10-03T18:00:00-05:00 (read in…
- `duration_hours` (number): How long the activity lasts. Defaults to the usual length for the activity, and says so.
- `intensity` (string): How hard the effort is, which changes what to wear. Defaults to the usual effort for the activity.
- `latitude` (number): Latitude in degrees. Use with longitude instead of location.
- `location` (string): A place name such as "Glenbeulah, WI" or "Greenbush, Wisconsin", or coordinates as "43.79,-88.05". Add the state or country for small towns, because a bare "Greenbush" matches several places.
- `longitude` (number): Longitude in degrees, west negative. Use with latitude instead of location.
- `units` (string): imperial (F, mph, inches) or metric (C, km/h, mm). Defaults to imperial in the United States and metric elsewhere.

### `clothing_recommendation` (~493 tokens)

What should I wear?

What to wear for an activity at a time and place, short and practical, followed by the weather it rests on. It dresses you for the effort, not just the temperature: a runner is warmer than a person standing still at the same feels-like, and the same rules as the website's outfit card apply. Optional: intensity, and preferences such as { "feel": "runs_cold" } or { "avoid": ["shorts"] }.

Input parameters:

- `activity` (string): What the person is doing, if known. One of: walking, hiking, trail_running, road_running, cycling, camping, hunting, fishing, yard_work, construction, painting_finishing, general_outdoor. Plain words…
- `duration_hours` (number): How long they will be out. Defaults to the usual length for the activity.
- `intensity` (string): How hard the effort is, which changes what to wear. Defaults to the usual effort for the activity.
- `latitude` (number): Latitude in degrees. Use with longitude instead of location.
- `location` (string): A place name such as "Glenbeulah, WI" or "Greenbush, Wisconsin", or coordinates as "43.79,-88.05". Add the state or country for small towns, because a bare "Greenbush" matches several places.
- `longitude` (number): Longitude in degrees, west negative. Use with latitude instead of location.
- `preferences` (object): Optional: { "feel": "runs_cold" | "runs_warm", "avoid": ["shorts"] }.
- `start_time` (string): When. Defaults to now. An ISO 8601 time such as 2026-10-03T18:00:00-05:00 (read in the place's own time zone when it has no offset), or plain words: "now", "tonight", "tomorrow morning", "Saturday",…
- `units` (string): imperial (F, mph, inches) or metric (C, km/h, mm). Defaults to imperial in the United States and metric elsewhere.

### `explain_weather` (~503 tokens)

Explain the weather

Explains weather in plain terms for conversation: why it feels colder than the temperature, whether rain will matter on a hike, whether wind matters, whether the trail will be muddy, humidity, fog, frost, pressure. It separates what the forecast says (facts, each labelled forecast or formula) from what we are reasoning (inferences, each with its basis and how sure we are) and lists what we cannot see (unknowns). Pass the question as asked, or a topic. If it cannot tell what was asked it says so and gives the general picture.

Input parameters:

- `activity` (string): What the person is doing, if known. One of: walking, hiking, trail_running, road_running, cycling, camping, hunting, fishing, yard_work, construction, painting_finishing, general_outdoor. Plain words…
- `duration_hours` (number): How many hours to look at. Default 6.
- `latitude` (number): Latitude in degrees. Use with longitude instead of location.
- `location` (string): A place name such as "Glenbeulah, WI" or "Greenbush, Wisconsin", or coordinates as "43.79,-88.05". Add the state or country for small towns, because a bare "Greenbush" matches several places.
- `longitude` (number): Longitude in degrees, west negative. Use with latitude instead of location.
- `question` (string): The question as the person asked it, for example "Why does it feel colder than the temperature?".
- `start_time` (string): The time the question is about. Defaults to now. An ISO 8601 time such as 2026-10-03T18:00:00-05:00 (read in the place's own time zone when it has no offset), or plain words: "now", "tonight", "tomor…
- `topic` (string): The topic, if you know it. Otherwise it is read from the question.
- `units` (string): imperial (F, mph, inches) or metric (C, km/h, mm). Defaults to imperial in the United States and metric elsewhere.

### `get_trail_weather` (~832 tokens)

Weather on a trail

Weather for a trail over time, sampled along the trail rather than at one point: starting conditions, how the temperature changes through the trip, rain windows, wind and gusts, humidity and dew point, wind chill and heat index, sunrise, sunset, twilight, the moon, significant changes, alerts, and what to wear and carry. Give a trail_id (call list_trails) or the route itself, plus start_time and a pace or total_duration_hours. Returns a timeline every two hours and a bottom line. It does not know the terrain, shade or exposure unless the trail record says so, and it says that.

Input parameters:

- `activity` (string): What the person is doing, if known. One of: walking, hiking, trail_running, road_running, cycling, camping, hunting, fishing, yard_work, construction, painting_finishing, general_outdoor. Plain words…
- `break_minutes_per_hour` (number): Minutes of stops per hour of moving, which stretches arrival times.
- `coordinates` (array): A list of [latitude, longitude] pairs, latitude FIRST.
- `geojson`: GeoJSON as an object or a string: a LineString, MultiLineString, or Features holding them. Longitude first, as GeoJSON has it.
- `gpx` (string): The text of a GPX file (track points). Up to about 450 KB.
- `intensity` (string): How hard the effort is, which changes what to wear. Defaults to the usual effort for the activity.
- `out_and_back` (boolean): True if the route is walked out and then back along the same line.
- `pace` (object): How fast the person moves, as a value and a unit.
- `polyline` (string): An encoded polyline (Google format).
- `polyline_precision` (integer): Digits of precision in the polyline. 5 is usual, 6 is what some routers send.
- `preferences` (object): Optional: { "feel": "runs_cold" | "runs_warm", "avoid": ["shorts"] }.
- `progress` (object): For someone already on the route: how far along they are right now. The answer is for the rest of the route, starting now. Give distance_miles or distance_km, or a latitude and longitude. The positio…
- `rest_at_turnaround_hours` (number): Hours spent resting at the turn of an out-and-back (a night's sleep, say).
- `start_time` (string): When the trip starts. Defaults to now. An ISO 8601 time such as 2026-10-03T18:00:00-05:00 (read in the place's own time zone when it has no offset), or plain words: "now", "tonight", "tomorrow mornin…
- `step_hours` (number): Hours between timeline rows. Default 2.
- `total_duration_hours` (number): Instead of a pace: how long the whole trip is expected to take. The pace is worked out from the length of the route.
- `trail_id` (string): A trail we know by name. Call list_trails to see them. Use this OR one of the route formats below.
- `units` (string): imperial (F, mph, inches) or metric (C, km/h, mm). Defaults to imperial in the United States and metric elsewhere.
- `waypoints` (array): Two to twelve places to travel between, each a name like "Glenbeulah, WI" or { "latitude": 43.79, "longitude": -88.05 }. They are joined by straight lines, so distances are approximate.

### `route_weather` (~871 tokens)

Weather along a route

What weather you will meet as you move along a route, at the moment you reach each part of it. Not "the weather on the trail" but "what will I encounter, where, and when". Accepts a known trail_id, a GPX file, GeoJSON, an encoded polyline, coordinates, or place names. With a start_time and a pace it works out when you reach each checkpoint, reads the forecast for that place at that time, and reports what changes: rain starting, the cold coming in, the light going. For someone already out there, pass `progress` (how far they are, or where) and it answers for the rest of the route from now. Returns checkpoints with arrival time, place, weather and light, the changes, and a bottom line. Use get_trail_weather for an hour-by-hour timeline and clothing advice.

Input parameters:

- `activity` (string): What the person is doing, if known. One of: walking, hiking, trail_running, road_running, cycling, camping, hunting, fishing, yard_work, construction, painting_finishing, general_outdoor. Plain words…
- `break_minutes_per_hour` (number): Minutes of stops per hour of moving, which stretches arrival times.
- `coordinates` (array): A list of [latitude, longitude] pairs, latitude FIRST.
- `geojson`: GeoJSON as an object or a string: a LineString, MultiLineString, or Features holding them. Longitude first, as GeoJSON has it.
- `gpx` (string): The text of a GPX file (track points). Up to about 450 KB.
- `intensity` (string): How hard the effort is, which changes what to wear. Defaults to the usual effort for the activity.
- `out_and_back` (boolean): True if the route is walked out and then back along the same line.
- `pace` (object): How fast the person moves, as a value and a unit.
- `polyline` (string): An encoded polyline (Google format).
- `polyline_precision` (integer): Digits of precision in the polyline. 5 is usual, 6 is what some routers send.
- `preferences` (object): Optional: { "feel": "runs_cold" | "runs_warm", "avoid": ["shorts"] }.
- `progress` (object): For someone already on the route: how far along they are right now. The answer is for the rest of the route, starting now. Give distance_miles or distance_km, or a latitude and longitude. The positio…
- `rest_at_turnaround_hours` (number): Hours spent resting at the turn of an out-and-back (a night's sleep, say).
- `start_time` (string): When the trip starts. Defaults to now. Ignored when progress is given. An ISO 8601 time such as 2026-10-03T18:00:00-05:00 (read in the place's own time zone when it has no offset), or plain words: "n…
- `total_duration_hours` (number): Instead of a pace: how long the whole trip is expected to take. The pace is worked out from the length of the route.
- `trail_id` (string): A trail we know by name. Call list_trails to see them. Use this OR one of the route formats below.
- `units` (string): imperial (F, mph, inches) or metric (C, km/h, mm). Defaults to imperial in the United States and metric elsewhere.
- `waypoints` (array): Two to twelve places to travel between, each a name like "Glenbeulah, WI" or { "latitude": 43.79, "longitude": -88.05 }. They are joined by straight lines, so distances are approximate.

### `list_trails` (~62 tokens)

Trails we know

Lists the trails WTDS knows by name, with length, bounds and whether we have data on which sections are exposed. Use a trail's id as trail_id in get_trail_weather or route_weather. If a trail is not listed, send the route itself.

### `search` (~66 tokens)

Find a place to get the weather for

Compatibility tool for ChatGPT connectors. Finds places matching a query and returns ids to pass to `fetch`. For real use prefer get_weather, outdoor_activity_weather and the other tools, which answer directly.

Input parameters:

- `query` (string, required): A place name, such as "Greenbush, WI".

### `fetch` (~54 tokens)

Get the weather for a place found by search

Compatibility tool for ChatGPT connectors. Returns the weather for an id from `search`. For real use prefer get_weather.

Input parameters:

- `id` (string, required): An id from `search`, like place:43.79,-88.05.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-weatherthatdoesntsuck-weather/api-mcp#diagnostics

## Score history

- 2026-11-04: 83
- 2026-11-03: 84
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 81
- 2026-10-28: 81
- 2026-10-27: 80
- 2026-10-26: 80
- 2026-10-25: 79
- 2026-10-24: 79
- 2026-10-23: 78
- 2026-10-22: 78
- 2026-10-21: 77
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 76
- 2026-10-17: 76
- 2026-10-16: 75
- 2026-10-15: 75
- 2026-10-14: 74
- 2026-10-13: 74
- 2026-10-12: 73
- 2026-10-10: 72
- 2026-10-08: 71
- 2026-10-06: 70
- 2026-10-04: 70

## Common questions

### What is the Weather That Doesn't Suck MCP server?

Weather That Doesn't Suck is an MCP server listed in the public MCP registry as com.weatherthatdoesntsuck/weather. Weather decisions for outdoor plans: should I go, when, what to wear, what you will meet en route. This page covers its hosted endpoint (https://weatherthatdoesntsuck.com/api/mcp).

### Is the Weather That Doesn't Suck MCP server safe to use?

Weather That Doesn't Suck scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Weather That Doesn't Suck MCP server expose?

Weather That Doesn't Suck exposes 11 tools: get_weather, get_forecast, outdoor_activity_weather, find_best_weather_window, clothing_recommendation, and 6 more. Their descriptions and schemas cost roughly 4,647 tokens of context every time the server is loaded.

### Does the Weather That Doesn't Suck MCP server require authentication?

No. We connected to Weather That Doesn't Suck without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Weather That Doesn't Suck MCP server still maintained?

Weather That Doesn't Suck is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://weatherthatdoesntsuck.com/api/mcp
- Website: https://weatherthatdoesntsuck.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-weatherthatdoesntsuck-weather/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-weatherthatdoesntsuck-weather/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-weatherthatdoesntsuck-weather/api-mcp