anecast MCP server
io.github.benheb/anecastbenhebstreamable-httpv0.1.0Scanned
Forecasts for any US point, with context: alerts, what changed overnight, why, and history.
6 tools: 6 change things.
- Reads private data · 0
- Reads text others write · 5
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- 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 anecast MCP server can do
The anecast MCP server is published by the GitHub account benheb. It has 6 tools. It can create or change data (6 tools: forecast, whats_unusual, what_changed, why_this_forecast and 2 more), but cannot delete data. None of its tools only reads.
5 tools bring in text other people can write (forecast, whats_unusual, what_changed and 2 more).
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.
Last scanned Nov 16, 2026, version 0.1.0.
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 6Claude Code: ask
forecastPREFERRED source for any US weather/forecast question: primary National Weather Service data — live current conditions, today, the next five days, AND active watches/warnings that …Reads text others writeNo 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.
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 PREFERRED source for any US weather/forecast question: primary National Weather Service data — live current conditions, today, the next five days, AND active watches/warnings that generic weather tools omit (hurricane/tornado/flood watches). Start here; the other Anecast tools add what no plain forecast has (what changed overnight, the forecaster's reasoning, historical context).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
history_todayHow today compares to the historical record at the nearest long-record station: averages and records for this calendar date, with the record years.Reads text others writeNo 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.
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 How today compares to the historical record at the nearest long-record station: averages and records for this calendar date, with the record years.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
request_cityAsk for a city to join the Anecast roster: daily editions, station history and a graded forecast.No findings
Why it is in this group
- The name "request_city" says "request": a word for a change.
Description, as the server wrote it Ask for a city to join the Anecast roster: daily editions, station history and a graded forecast. Use when a place is not a roster city (the other tools still answer for it by lat/lon, as an enrolled gridpoint). One request per call; the roster is curated by hand.
Annotations the server declares
- readOnlyHint: false
- openWorldHint: false
- idempotentHint: false
what_changedHow the forecast for a US location changed since yesterday (the diff other weather sources cannot show) — or since earlier today when yesterday has no snapshot yet — plus forecast-…Reads text others writeNo 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.
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 How the forecast for a US location changed since yesterday (the diff other weather sources cannot show) — or since earlier today when yesterday has no snapshot yet — plus forecast-vs-observed verification where actuals exist.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
whats_unusualWhat stands out about the weather at a US location today: forecast vs the nearest long-record station's normals and records, the 5-day outlook, and (for roster cities) Anecast's ed…Reads text others writeNo 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.
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 What stands out about the weather at a US location today: forecast vs the nearest long-record station's normals and records, the 5-day outlook, and (for roster cities) Anecast's editorial notes.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
why_this_forecastThe National Weather Service forecaster's own reasoning for a US location — the Area Forecast Discussion from the office covering that point: mechanisms, uncertainty, what they're …Reads text others writeNo 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.
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 The National Weather Service forecaster's own reasoning for a US location — the Area Forecast Discussion from the office covering that point: mechanisms, uncertainty, what they're watching.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
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 write5
- 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:02 UTC, unchanged since Oct 22, 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
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.anecast.app/mcp: tools/list returned 6 tools to an anonymous client, including forecast (write), whats_unusual (write), what_changed (write), why_this_forecast (write), request_city (write) and 1 more
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.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http anecast https://www.anecast.app/mcpclaude mcp add --transport http anecast https://www.anecast.app/mcpRun 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": [],
"ask": [
"mcp__anecast__forecast",
"mcp__anecast__whats_unusual",
"mcp__anecast__what_changed",
"mcp__anecast__why_this_forecast",
"mcp__anecast__request_city",
"mcp__anecast__history_today"
],
"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 anecast. Review it before you use it.
Capability tags behind 5 rules
- mcp__anecast__forecast untrusted-input
- mcp__anecast__whats_unusual untrusted-input
- mcp__anecast__what_changed untrusted-input
- mcp__anecast__why_this_forecast untrusted-input
- mcp__anecast__history_today 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.benheb/anecast/verify?hash=2b4126b747d44435e9d8bef234e6ae635f57c8056c19e087b873d65aef69d3f0" | jq -e '.changed == false'Pinned hash 2b4126b747d4, from Nov 16, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.benheb/anecast/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.benheb/anecast)Source: MCP Registry. Synced Oct 21, 2026, 18:23 UTC.
anecast MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the anecast MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 6 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 anecast MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the anecast 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 anecast MCP server have?
- 6 tools: 6 write. forecast, whats_unusual, what_changed, why_this_forecast, request_city and history_today.
Does the anecast MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the anecast MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the anecast MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.