Japan MOF Sanctions List Relay

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

Is this name on Japan's MOF asset-freeze list? Hosted, list-change history kept. Reference only.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that lets an assistant screen names against Japan's MOF asset-freeze list and review list changes over time.

What you can do
  • Screen a person or entity name, in Latin or Japanese, against the Japan MOF asset-freeze list under the Foreign Exchange Act, returning exact matches, similar-name candidates, no match, or unknown when the list is stale or unavailable.
  • Review what was added, removed or modified in the list since a given date, based on the service's own record of list versions.
  • Inspect the server's catalog of tools, prices, data sources, licensing, daily limits and data freshness.
  • Re-fetch the stored result of a settled paid call by its receipt id when a response was lost.
When to use it
Useful when an assistant needs a quick reference check on whether a name appears on Japan's asset-freeze list, or needs to see how that list changed since a date. Suited to compliance-adjacent research and screening workflows rather than authoritative determinations.
Requirements
A remote streamable HTTP endpoint; no local package, account, API key or header is declared. Network access is required. Some calls are paid, and the catalog tool lists prices and daily limits.
Before you install
The service describes itself as reference only, so results should not be treated as a compliance determination. Some calls are paid, so check prices and daily limits before use; stored results of settled calls are kept for 90 days. Screening results are sent to a third-party hosted service.

Installation

In SourceWeft

  1. Open Japan MOF Sanctions List Relay 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%2Fjp-sanctions/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": {
    "japan-mof-sanctions-list-relay": {
      "type": "http",
      "url": "https://jp-sanctions-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.

sanctions_screen_name

Screen a name against the MOF asset-freeze list

Does this person or entity name (Latin or Japanese) appear on the Japan MOF asset-freeze list under the Foreign Exchange Act? Returns exact_match, candidates (similar names, not matches), no_match_in_checked_list or unknown (stale/unavailable), with entry ids, all name forms, program, notice dates, list version, freshness and attribution. Reference relay only: not a compliance determination or a statement that a transaction is permitted.

Parametersnamerequiredmax_candidates

sanctions_list_changes

MOF asset-freeze list changes since a date

What was added to, removed from or modified in the Japan MOF asset-freeze list since a date? From this service's own record of list versions (MOF publishes only the current list). Each change has the entry id, names, program, before/after fields and the versions compared. History starts at tracking_since; nothing earlier was observed. Free window: last 30 days (an earlier since is clamped; see history_window). Reference relay only.

Parameterslimitsincerequiredentry_idchange_type

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.