Skip to content

Japan Weather Forecast Archive (JMA, as issued)

by mk-career-planning · remote · no sign-in to list tools · v0.1.0 · published by GitHub user mk-career-planning

What did Japan's weather agency forecast, as issued at a past time? Archive of JMA bulletins.

Changes · 2

4 tools: 2 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http jp-forecast-archive https://jp-forecast-archive-production.mk-career-planning.workers.dev/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 2Claude Code: ask
  • forecast_as_issuedArchived JMA prefectural weather forecast as issued.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
    Archived JMA prefectural weather forecast as issued. Give an area and at (forecast in effect then) or issued_at (exact JMA issue time). Returns JMA's bulletin as published (Japanese weather text, wind, waves, 6-hour rain probability, temperatures) with report_datetime (JMA's issue time) apart from fetched_at (ours). Status found, not_archived (before this archive started), unknown or no_issuance_at_that_time. Not the current forecast: check JMA.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • forecast_issuancesWhich prefectural weather forecasts did JMA issue for an area between two times?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
    Which prefectural weather forecasts did JMA issue for an area between two times? Lists each archived issuance (JMA issue time, transmission time, our fetch time, scheduled/unscheduled/correction/cancellation, bulletin URL and SHA-256) with coverage gaps where JMA's feed could not be read. Free window: last 30 days (an earlier since is clamped; see history_window). Use forecast_as_issued for the content. An archive, not a forecast service.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Only reads 2Claude Code: allow
  • catalogList the tools of this server with prices, data sources, licensing, daily limits and data freshness.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List the tools of this server with prices, data sources, licensing, daily limits and data freshness.

    Annotations the server declares

    • readOnlyHint: true
  • get_receiptRe-fetch the stored result of a settled paid call by its receipt_id, for when the response was lost after payment.No findings

    Why it is in this group

    • The name "get_receipt" says "get": a word for reading.
    Description, as the server wrote it
    Re-fetch the stored result of a settled paid call by its receipt_id, for when the response was lost after payment. Free. Unknown or unsettled receipt ids return RECEIPT_NOT_FOUND. Results are kept for 90 days after settlement.

    Annotations the server declares

    • readOnlyHint: 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.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http jp-forecast-archive https://jp-forecast-archive-production.mk-career-planning.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__jp-forecast-archive__catalog",
      "mcp__jp-forecast-archive__get_receipt"
    ],
    "ask": [
      "mcp__jp-forecast-archive__forecast_as_issued",
      "mcp__jp-forecast-archive__forecast_issuances"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as jp-forecast-archive. Review it before you use it.