Smarter Weather MCP server
io.github.smarterweather/weathersmarterweatherstreamable-httpv0.1.1Scanned
Smarter Weather MCP: forecasts, alerts, outlooks, observations, AQI, grids, and map imagery.
6 tools: 1 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Smarter Weather MCP server can do
The Smarter Weather MCP server is published by the GitHub account smarterweather. It has 6 tools. It can create or change data (1 tool: render), but cannot delete data. 5 tools only read.
3 tools bring in text other people can write (describe_data, get_context and get_status).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 0.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 1Claude Code: ask
renderRender a weather map or chart image for visual analysis: `kind: map` draws `select` layers (radar, satellite, outlooks, alerts and storm features overlaid) at `location` or `bbox`,…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Render a weather map or chart image for visual analysis: `kind: map` draws `select` layers (radar, satellite, outlooks, alerts and storm features overlaid) at `location` or `bbox`, and `kind: sounding` draws the nearest radiosonde as a skew-T and hodograph chart. With no `select` the map draws `precipitation_hybrid` (observed radar precipitation in the place's domain); `at` picks the closest frame, `filter` narrows feature overlays, `area` draws an outline, and search_data finds products. Example: {"kind": "map", "location": "Tulsa, OK", "select": ["nexrad_l3:TLX:N0S", "weather_alert"], "filter": ["event == Tornado Warning"], "zoom": 8}.
Annotations the server declares
- title: Visuals
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 5Show 5 read-only tools
describe_dataA dataset's variables or properties (standard names, units, categories, bands, aggregates), horizon, step, cadence, freshness, cost class, verified `examples`, an example_query to …Reads text others writeNo findings
Why it is in this group
- The name "describe_data" says "describe": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it A dataset's variables or properties (standard names, units, categories, bands, aggregates), horizon, step, cadence, freshness, cost class, verified `examples`, an example_query to read values; a map layer's axes (source, region, facts), render call. Free. Call it when a grid or snapshot hit's `call` lacks the variable you need (with no `variable`, it may read only the headline one), or to check meaning, units, horizon or cost; not needed when the hit's `call` already names what you need: run that. Example: {"dataset_id": "<from search_data>"}.
Annotations the server declares
- title: Details
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
- destructiveHint: false
get_contextWhere a place is and what time it is there.Reads text others writeNo findings
Why it is in this group
- The name "get_context" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Where a place is and what time it is there. `location` or `lat`+`lon` to ranked `candidates` with lat/lon, timezone and `type` place|zip|address|poi|county|station; `time`: `utc` and, per distinct zone among the candidates, its local time and a 14-day calendar (join on `timezone`). Sun and moon are get_data reads. Example: {"location": "Pella, IA"} -> Pella, America/Chicago.
Annotations the server declares
- title: Place & time
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
- destructiveHint: false
get_dataValues, totals, comparisons, best times for a purpose (`criteria`), people/POI counts, station observations, upper-air profiles, climate records, normals, degree days, teleconnecti…No findings
Why it is in this group
- The name "get_data" says "get": a word for reading.
Description, as the server wrote it Values, totals, comparisons, best times for a purpose (`criteria`), people/POI counts, station observations, upper-air profiles, climate records, normals, degree days, teleconnection indices and forecaster text from any dataset (models, radar, alerts, outlooks, tropical cyclones, aircraft recon, reference layers) at places, over a bbox or area, along a path, or as items. `select` takes `product:variable` or `product:property`, a standard name or a concept (`population`), from describe_data or search_data; one space word, at most one time word (hours, start+end, at; run pins a cycle); `stats` reduces per `step` or area-wide. Example: {"select": ["temperature_2m"], "locations": ["Savannah, GA", "Macon, GA"], "hours": 36}.
Annotations the server declares
- title: Weather
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
- destructiveHint: false
get_statusData freshness of the weather platform (no inputs needed; refreshed about every 5 minutes): overall state, per-source states (ok / degraded / outage / no_signal), open incidents wi…Reads text others writeNo findings
Why it is in this group
- The name "get_status" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Data freshness of the weather platform (no inputs needed; refreshed about every 5 minutes): overall state, per-source states (ok / degraded / outage / no_signal), open incidents with their cause (provider outage vs internal processing delay) and active provider advisories. Use it when asked whether data is current, or when other tools return stale-looking data. If a source is degraded or in outage, say the data may be stale rather than presenting it as live. Example: {}.
Annotations the server declares
- title: Status
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
- destructiveHint: false
search_dataSearch the data catalog: which dataset's values answer a question about weather and the people and places it affects, or what data exists at a point.No findings
Why it is in this group
- The name "search_data" says "search": a word for reading.
Description, as the server wrote it Search the data catalog: which dataset's values answer a question about weather and the people and places it affects, or what data exists at a point. With `query` it ranks datasets and map layers and returns hits with the next `call` (a named place fills its `area`; add a place if `note` asks) and any verified `example`; without it, it lists datasets at the place with freshness, or all. A place or `domain` keeps datasets covering it; `kind` and `family` filter a listing, rank a query; describe_data lists other variables for get_data. Example: {"query": "snow depth", "location": "Erie, PA"}.
Annotations the server declares
- title: Search
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
- destructiveHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:11 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.smarterweather.com/.well-known/oauth-protected-resource
- Authorization servers
- https://clerk.smarterweather.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- no
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.smarterweather.com: tools/list returned 6 tools to an anonymous client, including render (write)
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 0 to 1
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 added, 9 removed, 4 changed.+2 added−9 removed~4 changedView diff
- Added:get_contextOnly reads
- Added:renderChanges things
- Removed:call_tool
- Removed:find_places
- Removed:find_tools
- Removed:get_alerts
- Removed:get_current_conditions
- Removed:get_forecast
- Removed:get_forecast_distribution
- Removed:get_observed_precipitation
- Removed:get_time_context
- Changed:describe_dataOnly readstitledescriptioninputSchemaannotations
- Changed:get_dataOnly readstitledescriptioninputSchemaannotations
- Changed:get_statusOnly readstitledescriptionannotations
- Changed:search_dataOnly readstitledescriptioninputSchemaannotations
Tools7 added, 8 removed, 6 changed.+7 added−8 removed~6 changedView diff
- Added:call_toolChanges things
- Added:describe_dataOnly reads
- Added:find_placesOnly reads
- Added:find_toolsOnly reads
- Added:get_dataOnly reads
- Added:get_statusOnly reads
- Added:search_dataOnly reads
- Removed:describe_dataset
- Removed:get_hourly_forecast
- Removed:get_platform_status
- Removed:list_datasets
- Removed:query_dataset
- Removed:reverse_geocode
- Removed:search_catalog
- Removed:search_locations
- Changed:get_alertsOnly readsdescriptioninputSchema
- Changed:get_current_conditionsOnly readsdescriptioninputSchema
- Changed:get_forecastOnly readsdescriptioninputSchema
- Changed:get_forecast_distributionOnly readsdescriptioninputSchema
- Changed:get_observed_precipitationOnly readsdescriptioninputSchema
- Changed:get_time_contextOnly readsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1.View diff
- Tools that change things, listed without credentials: 0 to 1
Install
Pinned to version 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http weather https://mcp.smarterweather.comclaude mcp add --transport http weather https://mcp.smarterweather.comRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__weather__search_data",
"mcp__weather__describe_data",
"mcp__weather__get_context",
"mcp__weather__get_data",
"mcp__weather__get_status"
],
"ask": [
"mcp__weather__render"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as weather. Review it before you use it.
Capability tags behind 3 rules
- mcp__weather__describe_data untrusted-input
- mcp__weather__get_context untrusted-input
- mcp__weather__get_status untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.smarterweather/weather/verify?hash=719b76e75ce0877726fde28b7b161f235fbedb6ea14655ecca6d95c0ef69dd25" | jq -e '.changed == false'Pinned hash 719b76e75ce0, from Nov 20, 2026, 13:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.smarterweather/weather/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.smarterweather/weather)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:49 UTC.
Smarter Weather MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Smarter Weather MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Smarter Weather MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Smarter Weather MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Smarter Weather MCP server have?
- 6 tools: 1 write, 5 read. render, search_data, describe_data, get_context, get_data and get_status.
Does the Smarter Weather MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Smarter Weather MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Smarter Weather MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.