AccuWeather Core Weather API + MCP vs Pirate Weather

AccuWeather Core Weather API + MCP

Official hosted MCP server, 26 read-only tools, same key as the REST API. Terms forbid using the data to train, validate or otherwise inform any AI system.

Pirate Weather

Named model sources and a documented priority order for every field. No SLA, and the terms call it best effort.

AccuWeather Core Weather API + MCP

1. Cache location keys. They don't change, and the lookup is the call worth saving
2. Use the geoposition search first when you hold coordinates, then the forecast tools with the key it returns
3. Send the key as a Bearer header, not in the MCP URL, so it stays out of logs
4. Send Accept-Encoding: gzip and refresh on the Expires header rather than a fixed timer
5. Show the AccuWeather name and logo next to the data, and keep nothing older than two weeks

Pirate Weather

1. Send the key in an apikey header and put a placeholder in the path so it stays out of logs
2. Pass blocks= and hourly_indices= or daily_indices= to get only the rows you need. The default payload is large
3. Ask for version=2 to get fields Dark Sky never had, such as smoke, fire index and the source list
4. Point historical requests at timemachine.pirateweather.net with a UNIX timestamp after the coordinate
5. Watch Ratelimit-Remaining. The cap is monthly, so a runaway loop can spend it in a day