accueil / serveurs / Géo & Temps / io.github.mk-career-planning/jp-forecast-archive
io.github.mk-career-planning/jp-forecast-archive
serveur MCP (Model Context Protocol) · jp-forecast-archive 0.1.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.mk-career-planning/jp-forecast-archive est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.mk-career-planning/jp-forecast-archive » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 4 outils
- catalog≈ 799 tokens
List the tools of this server with prices, data sources, licensing, daily limits and data freshness.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "catalog", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"legal": {}, "terms": "texte", "tools": [], "paused": {}, "server": {}, "payment": {}, "provenance": [], "daily_limits": {}, "fetch_status_values": {}}} - forecast_as_issued≈ 1646 tokens
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.
Paramètres, retour & exemple (3)
Paramètresat· string · optionnel
ISO 8601 date-time with time zone: return the issuance in effect at this time, e.g. 2026-10-12T09:00:00+09:00area· string · requis
JMA forecast office code (130000), sub-area code (130010), prefecture (Tokyo, 東京都, 13) or JMA area name (Kushiro Nemuro). Prefectures with several offices (Hokkaido, Kagoshima, Okinawa) need the office or sub-areaissued_at· string · optionnel
ISO 8601 date-time with time zone: return the issuance with exactly this JMA issue time, e.g. 2026-10-12T05:00:00+09:00
Exemple d'appel{"name": "forecast_as_issued", "arguments": {"area": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": {}, "terms": "texte", "status": "found", "archive": {}, "issuance": "texte", "provenance": [], "answered_at": "texte", "attribution": {}, "status_note": "texte", "legal_notice": "texte", "archive_notice": "texte", "official_check": {}}} - forecast_issuances≈ 1655 tokens
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.
Paramètres, retour & exemple (4)
Paramètresarea· string · requis
JMA forecast office code (130000), sub-area code (130010), prefecture (Tokyo, 東京都, 13) or JMA area name (Kushiro Nemuro). Prefectures with several offices (Hokkaido, Kagoshima, Okinawa) need the office or sub-arealimit· integer · optionnel
Maximum number of issuances, 1-500 (default 100)since· string · requis
Issuances after this: ISO 8601 date (00:00 Japan time) or date-time with time zone, e.g. 2026-10-12 or 2026-10-12T05:00:00+09:00until· string · optionnel
Optional end: ISO 8601 date (00:00 Japan time) or date-time with time zone (default now)
Exemple d'appel{"name": "forecast_issuances", "arguments": {"area": "texte", "since": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": {}, "terms": "texte", "archive": {}, "coverage": {}, "issuances": [], "truncated": true, "provenance": [], "answered_at": "texte", "attribution": {}, "legal_notice": "texte", "archive_notice": "texte", "history_window": {}}} - get_receipt≈ 676 tokens
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.
Paramètres, retour & exemple (1)
Paramètresreceipt_id· string · requis
The receipt_id returned with a paid result ("rcpt_" + 64 hex characters).
Exemple d'appel{"name": "get_receipt", "arguments": {"receipt_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"tool": "texte", "terms": "texte", "result": "texte", "payment": {}, "provenance": [], "receipt_id": "texte", "settled_at": "texte"}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».
Source
https://jp-forecast-archive-production.mk-career-planning.workers.dev/mcp