MOFA Overseas Safety Levels

io.github.mk-career-planningPublished by GitHub account mk-career-planningv0.1.0Updated Oct 24, 2026

Which danger level has Japan's MOFA set for a country and its regions? Hosted, change history kept.

The publisher's own server: Levels.fyi

VerifiedStreamable HTTPWeb executableLocation & LifestyleWeb Search & Scraping

Overview

AI-generated overview

Remote MCP server that lets an assistant look up Japan MOFA overseas danger levels by country and region, and track level changes over time.

What you can do
  • Look up Japan MOFA danger levels (1-4) for a country, region by region, by ISO alpha-2/alpha-3 or 4-digit MOFA code, with Japanese source text, English level labels and a derived maximum level.
  • List countries whose danger or infectious disease levels, or region texts, changed since a given time, based on the service's own observation record.
  • Retrieve a stored result of a settled paid call by receipt id when the original response was lost.
  • List the server's tools with prices, data sources, licensing, daily limits and data freshness.
When to use it
Useful when an assistant needs current Japanese government travel-safety levels for a destination, or a history of which countries' levels changed recently, for travel planning, risk briefings or monitoring.
Requirements
A remote streamable HTTP endpoint; no local install, account, API key or environment variables are declared. Some calls are paid, and the catalog tool reports prices and daily limits.
Before you install
Some tools are paid calls, so using them can incur charges; the catalog tool should be checked for prices and limits first. Levels are region-level entries with a derived maximum, not an official country-wide level, and change history comes from the service's own polling record rather than MOFA directly. Paid results are only kept 90 days after settlement.

Installation

In SourceWeft

  1. Open MOFA Overseas Safety Levels in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mk-career-planning%2Fmofa-overseas-safety/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mofa-overseas-safety-levels": {
      "type": "http",
      "url": "https://mofa-overseas-safety-production.mk-career-planning.workers.dev/mcp"
    }
  }
}

Tools

4

catalog

Catalog: tools, prices and limits

List the tools of this server with prices, data sources, licensing, daily limits and data freshness.

Takes no parameters.

mofa_country_levels

MOFA danger levels for a country

Which danger level (1-4) does Japan's MOFA set now for this country, region by region? Look up by ISO 3166-1 alpha-2/alpha-3 or 4-digit MOFA code. Returns region-level entries in MOFA's Japanese text with English level labels, levels present, a derived max level (not a country-wide level), infectious disease danger notices, MOFA issue dates and URLs, previous levels from this service's own history (tracking_since), freshness and sources. Relays MOFA; no danger assessment or travel advice.

Parameterscountryrequired

mofa_level_changes

MOFA danger level changes since a time

Which countries had their Japan MOFA danger or infectious disease danger levels (or region texts) change since a given time? From this service's own observation record: old and new levels, MOFA info ids and issue dates, when we observed the change and when we last saw the old state, plus polling gaps. Only changes since tracking_since, as observed at our polling times. Free window: last 30 days (an earlier since is clamped; see history_window). Relays MOFA; no advice.

Parameterslimitsincerequiredcountryinclude_notice_updates

get_receipt

Get receipt of a paid call

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.

Parametersreceipt_idrequired

Version history

1
  1. v0.1.0LatestOct 12, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Levels integrations