Japan Weather & Alerts
REMOTE · TENKI-MCP.EASAKURA.WORKERS.DEV · 2 COMPONENTS · SCANNED AUG 3
Japan weather forecasts and disaster alerts from JMA: forecasts, warnings, and earthquake info.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 280 tokens (~93/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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · tenki-mcp.easakura.workers.dev
claude mcp add --transport http easakura-japan-weather-alerts-mcp https://tenki-mcp.easakura.workers.dev/sse
[mcp_servers.easakura-japan-weather-alerts-mcp] url = "https://tenki-mcp.easakura.workers.dev/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"easakura-japan-weather-alerts-mcp": {
"type": "remote",
"url": "https://tenki-mcp.easakura.workers.dev/sse",
"enabled": true
}
}
} openclaw mcp add easakura-japan-weather-alerts-mcp --url https://tenki-mcp.easakura.workers.dev/sse --transport streamable-http
mcp_servers:
easakura-japan-weather-alerts-mcp:
url: "https://tenki-mcp.easakura.workers.dev/sse" {
"mcpServers": {
"easakura-japan-weather-alerts-mcp": {
"type": "http",
"url": "https://tenki-mcp.easakura.workers.dev/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 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.
- 31 Jul 26 −4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Jul 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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 54
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 3 Aug 2026 · Probed https://tenki-mcp.easakura.workers.dev/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=easakura.workers.dev | CN=WE1,O=Google Trust Services,C=US | 13 Jul 2026 | 11 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 997e95d4e676a1e20e6b46db6f16ffd5 |
| SANs: easakura.workers.dev, *.easakura.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of tenki-mcp.easakura.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 404 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://tenki-mcp.easakura.workers.dev/sse | Verified | 200 | |
| http (plaintext) | http://tenki-mcp.easakura.workers.dev/sse | Served over HTTP | 200 |
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.
get_recent_earthquakes 最近の地震情報を取得 ~70
日本で最近観測された地震の一覧（発生時刻・震源地・マグニチュード・最大震度）を気象庁公式データから取得する。
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | — | 最大件数（1〜20） |
No output schema declared.
No examples provided.
get_weather_forecast 日本の天気予報を取得 ~113
気象庁公式データから指定地域の天気予報（今日・明日・明後日＋週間）を取得する。地域は都道府県名で指定（例: 東京都、大阪府、北海道は「石狩・空知・後志地方」等の予報区名）。
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | yes | 都道府県・予報区名（例: 東京都 / 大阪府 / 沖縄本島地方） |
No output schema declared.
No examples provided.
get_weather_warnings 気象警報・注意報を取得 ~97
指定地域に現在発表されている気象警報・注意報（大雨警報、洪水警報、雷注意報など）を気象庁公式データから取得する。防災判断・イベント開催判断・物流計画などに使う。
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | yes | 都道府県・予報区名（例: 東京都 / 大阪府） |
No output schema declared.
No examples provided.