io.github.mk-career-planning/japan-agent-api

Est-ce que io.github.mk-career-planning/japan-agent-api est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.mk-career-planning/japan-agent-api » 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 8 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": {}}}

• get_receipt≈ 683 tokens

  Re-fetch the stored result of a settled paid call (e.g. jp_trip_impact_check) 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ètres

  • receipt_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"}}

• jp_municipality≈ 1172 tokens

  Which code does this Japanese municipality have on a date (default today)? Give a 5/6-digit code, or prefecture and name (old names OK). Returns status mapped / split_candidates / unknown / invalid, the valid code with English and Japanese names, change type and date (merger, incorporation, division, designated city, name change), confirmed JMA warning areas only, and J-LIS convenience-store certificate availability for 8 certificate types. Facts only, from e-Stat LOD (CC BY 4.0) and J-LIS.

  Paramètres, retour & exemple (4)

  Paramètres

  • code · string · optionnel
    Municipality code: 5 digits, or 6 digits including the check digit (e.g. 22131 or 221317).
  • name · string · optionnel
    Municipality or ward name in Japanese (old names accepted; a ward may be prefixed with its city) or its e-Stat English name (e.g. "Naka-ku", "Hamamatsu-shi"). Use with prefecture.
  • as_of · string · optionnel
    YYYY-MM-DD. The date the answer is for (default: today in Japan time).
  • prefecture · string · optionnel
    Japanese prefecture: English name (e.g. "Tokyo", "Osaka", "Hokkaido"; "Tokyo-to" and "Osaka Prefecture" also work), Japanese name in kanji, or JIS code "01".."47". Use with name.

  Exemple d'appel

  {"name": "jp_municipality", "arguments": {"code": "texte", "name": "texte", "as_of": "texte", "prefecture": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"as_of": "texte", "input": {}, "terms": "texte", "source": "texte", "status": "mapped", "changes": [], "disclaimer": "texte", "provenance": [], "as_of_codes": [], "license_note": "texte", "out_of_scope": [], "responded_at": "texte"}}

• jp_municipality_batch≈ 1647 tokens

  Which codes are valid on a date for up to 50 Japanese municipalities? e-Stat LOD change history (CC BY 4.0): status mapped / split_candidates (all successors, not apportioned) / unknown / invalid, the code valid on as_of with English and Japanese names, change type and date, confirmed JMA warning areas only, and J-LIS convenience-store certificate availability (available / not_listed / unknown). Facts only; no document preparation or legal advice. Retrying with the same payment is not charged.

  Paramètres, retour & exemple (2)

  Paramètres

  • as_of · string · optionnel
    Default as_of for items that do not set their own.
  • items · array · requis
    1 to 50 lookups; each gives code, or prefecture and name.

  Exemple d'appel

  {"name": "jp_municipality_batch", "arguments": {"items": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• jp_trip_impact_check≈ 2044 tokens

  Does a JMA warning or advisory in effect now match a stop on this Japan itinerary [{date, prefecture}]? Per stop: matched_advisory (with severity), no_match_in_checked_sources (NOT a statement of no impact) or unknown (data missing, or date not today/tomorrow JST). Returns checked sources and areas, unchecked areas, issued_at, retrieved_at, and current JMA typhoon/volcano bulletins (listed, not matched). No forecast. Retrying with the same payment is not charged; use receipt_id with get_receipt.

  Paramètres, retour & exemple (1)

  Paramètres

  • itinerary · array · requis
    1 to 14 stops {date, prefecture}, in travel order. Only stops dated today or tomorrow (Japan time) can be matched; others return unknown, but typhoon and volcano bulletins currently in effect are still listed (not matched).

  Exemple d'appel

  {"name": "jp_trip_impact_check", "arguments": {"itinerary": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• jp_typhoons≈ 850 tokens

  Which typhoons is JMA issuing bulletins for right now, and what do the bulletins forecast? Number, name, center position, central pressure, maximum wind, issue time, and forecast-circle centers, radii and times, relayed as structured JSON from JMA bulletins (VPTW60-65). No independent forecast, interpolation or track extension.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "jp_typhoons", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "count": 1, "ended": [], "terms": "texte", "source": "texte", "status": "listed", "typhoons": [], "unchecked": [], "provenance": [], "license_note": "texte", "responded_at": "texte", "retrieved_at": "texte"}}

• jp_volcanoes≈ 1350 tokens

  What is the current JMA Volcanic Alert Level (1-5, or warning kind) of this volcano or of every JMA-monitored volcano? Name in English or Japanese, or 3-digit JMA code. Returns JMA English and Japanese names, level, previous level and change, issue time, prefectures named in JMA bulletins, source URL and freshness receipt. Relay only; no forecast or interpretation. Gaps filled from JMA website lists (newer wins). No JMA source seen = not_seen_in_checked_feeds, never assumed level 1.

  Paramètres, retour & exemple (1)

  Paramètres

  • volcano · string · optionnel
    Optional. JMA volcano name in English (e.g. "Sakurajima", "Asamayama") or Japanese (e.g. "桜島"), or the 3-digit JMA volcano code (e.g. "506"). Omit to list all volcanoes.

  Exemple d'appel

  {"name": "jp_volcanoes", "arguments": {"volcano": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "count": 1, "terms": "texte", "source": "texte", "coverage": {}, "volcanoes": [], "provenance": [], "license_note": "texte", "responded_at": "texte", "retrieved_at": "texte"}}

• jp_warnings≈ 1218 tokens

  Which JMA weather emergency warnings, warnings and advisories are in effect in this Japanese prefecture now? Structured JSON in English and Japanese (type, level, status, areas with JMA's English names, issued_at, source URL). Relay only; no independent forecast.

  Paramètres, retour & exemple (2)

  Paramètres

  • prefecture · string · requis
    Japanese prefecture: English name (e.g. "Tokyo", "Osaka", "Hokkaido"; "Tokyo-to" and "Osaka Prefecture" also work), Japanese name in kanji, or JIS code "01".."47".
  • include_municipalities · boolean · optionnel
    Also list every municipality (Japanese and English names) per warning. Default false.

  Exemple d'appel

  {"name": "jp_warnings", "arguments": {"prefecture": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"terms": "texte", "counts": {}, "region": "texte", "source": "texte", "coverage": "complete", "warnings": [], "bulletins": [], "prefecture": {}, "provenance": [], "license_note": "texte", "responded_at": "texte", "retrieved_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é ».

Créer un compte / revendiquer →

Source

https://japan-agent-api-production.mk-career-planning.workers.dev/mcp