AccuWeather MCP
OCI · DOCKER.IO/JONJAM/ACCUWEATHER-MCP:1.4.11
MCP server providing weather tools with data sourced from AccuWeather.
Available components
Last scanned (1 hour ago)
Scores higher than 66% of OCI servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency26
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Maintenance history not yet determined.Unverified
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 107 tokens (~35/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (11)
- Source repository
- Provenance
- License
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (5)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Maintenance in Provenance & TransparencyMaintenance history not yet determined.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 −2
- Stability: pass → 0.80 functional
- 17 Oct 26 +1
- Stability: 0.87 → pass security
- 16 Oct 26 +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.
- 15 Oct 26 −2
- Stability: pass → 0.83 functional
- 14 Oct 26 0
- Stability: 0.97 → pass security
- 13 Oct 26 +1
- Provenance: unverified → fail ▼ security
- Security disclosure: unverified → fail ▼ functional
- License: unverified → fail ▼ functional
- 12 Oct 26 −1
- Provenance: fail → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- License: fail → unverified ▼ functional
- Stability: pass → 0.93 functional
- 7 Oct 26 +1
- Stability: 0.90 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed oci/docker.io/jonjam/accuweather-mcp:1.4.11
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
current-conditions Current Weather Conditions ~30
Get the current weather conditions for a location.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | City or point of interest |
No output schema declared.
No examples provided.
daily-forecast Daily Weather Forecast ~30
Get the daily weather forecast for a location.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | City or point of interest |
No output schema declared.
No examples provided.
hourly-forecast Hourly Weather Forecast ~33
Get the 12-hour hourly weather forecast for a location.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | City or point of interest |
No output schema declared.
No examples provided.
How do I install the AccuWeather MCP server?
AccuWeather MCP runs locally as a container image, launched with docker run --rm -i -e ACCUWEATHER_API_KEY docker.io/jonjam/accuweather-mcp:1.4.11. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · docker.io/jonjam/accuweather-mcp:1.4.11
claude mcp add jonjam-accuweather-mcp -- docker run --rm -i -e ACCUWEATHER_API_KEY docker.io/jonjam/accuweather-mcp:1.4.11
This image reads ACCUWEATHER_API_KEY. Set it in your client's env block for this server; docker run -e passes it through to the container.
What is the AccuWeather MCP server?
AccuWeather MCP is listed in the public MCP registry as io.github.JonJam/accuweather-mcp. MCP server providing weather tools with data sourced from AccuWeather. This page covers its container image (docker.io/jonjam/accuweather-mcp:1.4.11).
Is the AccuWeather MCP server safe to use?
AccuWeather MCP scores 46 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 AccuWeather MCP server expose?
AccuWeather MCP exposes 3 tools: current-conditions, daily-forecast, hourly-forecast. Their descriptions and schemas cost roughly 93 tokens of context every time the server is loaded.
Is the AccuWeather MCP server still maintained?
AccuWeather MCP is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the AccuWeather MCP server?
VerifyMCP ran 11 checks on AccuWeather MCP, covering Source repository, Provenance, License, Security disclosure and 7 more. 5 items could not be completed, a gap on our side rather than a finding about AccuWeather MCP: Malware scan, Known CVEs, Install scripts, Dependency health and 1 more. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.