Jma
NPM · @PIPEWORX/MCP-JMA · 2 COMPONENTS
JMA (Japan Meteorological Agency) MCP — keyless weather forecasts, warnings, and earthquake data…
Available components
Last scanned (20 hours ago)
Scores higher than 72% of npm 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-jma). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 876 tokens (~219/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
First indexed and scored.
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 4 Nov 2026 · Analysed npm/@pipeworx/mcp-jma@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-jma |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-jma/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649486593 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9687e7d5fc9909b775181ddedf00a8ed3b615af4c9432601c6ed98463e33515332099b3609ab2317209152d0860545f12e624e817b8216cd2a951e2ac |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
jma_earthquakes ~242
Recent earthquakes reported by the Japan Meteorological Agency (JMA), including magnitude, maximum seismic intensity (震度, JMA's 10-step scale: 1-4, 5 Lower, 5 Upper, 6 Lower, 6 Upper, 7), epicenter (Japanese + English where JMA publishes one), and report time. Sourced from www.jma.go.jp/bosai/quake/data/list.json, which JMA keeps as a rolling feed (typically the last few weeks of bulletins, newest first). Filter by minimum magnitude or minimum intensity to cut noise from the very small, frequent events JMA also reports.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max events to return (default 20, max 200). |
| min_intensity | string | – | Only events whose max reported intensity is at least this JMA scale value: "1","2","3","4","5-","5+","6-","6+","7" (5- = 5 Lower, 5+ = 5 Upper, etc.). |
| min_magnitude | number | – | Only events with magnitude >= this value. |
No output schema declared.
No examples provided.
jma_forecast ~196
Weather forecast for a Japanese region from the Japan Meteorological Agency (JMA), covering a 3-day short-term outlook (weather, precipitation probability, temperature per sub-area) and a 7-day weekly outlook (weather, precipitation probability, reliability, min/max temperature with confidence range). Sourced from www.jma.go.jp/bosai/forecast/data/forecast/<office>.json. Accepts a place name in English or Japanese ("Tokyo", "Sapporo", "大阪") or a JMA office code directly — resolved the same way as jma_resolve_area. Weather text is native Japanese; an English gloss is included for JMA's fixed weatherCode set (weatherEn), derived from a static translation table, not machine-translated on the fly.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | yes | Place name or JMA area/office code, e.g. "Tokyo", "Fukuoka", "130000". |
No output schema declared.
No examples provided.
jma_resolve_area ~184
Resolve a Japanese place name (English romaji or Japanese, e.g. "Tokyo", "Sapporo", "大阪") or a JMA area code to the JMA forecast OFFICE code used by jma_forecast and jma_warnings. Sourced from the Japan Meteorological Agency (JMA) area master list (www.jma.go.jp/bosai/common/const/area.json), which covers all 58 forecast offices plus every prefecture, region, city, ward and town JMA itself names in English. Use this when you need the raw office code, or just pass the place name straight into jma_forecast / jma_warnings — they resolve internally.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Place name (English or Japanese) or JMA area code, e.g. "Tokyo", "Naha", "130000". |
No output schema declared.
No examples provided.
jma_warnings ~202
Current weather warnings and advisories (警報・注意報) for a Japanese region, from the Japan Meteorological Agency (JMA). Returns the headline bulletin plus per-area status (issued / continuing / lifted / no warnings in effect) for every warning/advisory category JMA tracks (heavy rain, storm, flood, wave, storm surge, dense fog, thunderstorm, avalanche, frost, etc.), at both the sub-prefecture and municipality level. Sourced from www.jma.go.jp/bosai/warning/data/warning/<office>.json. Accepts a place name (English or Japanese) or a JMA office code, resolved the same way as jma_resolve_area. Category and status names are native Japanese with an English gloss from JMA's fixed warning-code table.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | yes | Place name or JMA area/office code, e.g. "Osaka", "東京", "130000". |
No output schema declared.
No examples provided.
How do I install the Jma MCP server?
Jma runs locally as an npm package, launched with npx -y @pipeworx/mcp-jma. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-jma
claude mcp add pipeworx-io-jma -- npx -y @pipeworx/mcp-jma
What is the Jma MCP server?
Jma is an MCP server listed in the public MCP registry as io.github.pipeworx-io/jma. JMA (Japan Meteorological Agency) MCP, keyless weather forecasts, warnings, and earthquake data… This page covers its npm package (@pipeworx/mcp-jma).
Is the Jma MCP server safe to use?
Jma scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Jma MCP server expose?
Jma exposes 4 tools: jma_resolve_area, jma_forecast, jma_warnings, jma_earthquakes. Their descriptions and schemas cost roughly 824 tokens of context every time the server is loaded.
Is the Jma MCP server still maintained?
Jma 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.
What licence is the Jma MCP server under?
Jma declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.