Japan MOF Sanctions List Relay

What Japan MOF Sanctions List Relay MCP server does

Japan MOF Sanctions List Relay MCP server provides a reference lookup for checking whether a supplied name appears on Japan’s MOF asset-freeze list. The service is hosted rather than described as a package that must be installed locally. It also retains list-change history, which gives consumers a way to account for changes to the underlying list instead of treating the current result as the only available reference.

The supplied description identifies the service as reference-only. That makes it suitable for research, screening workflows, or agent responses that need to consult Japan’s sanctions data. It does not establish that the service performs a legal determination, blocks transactions, verifies identity, or evaluates names beyond the list lookup described.

How it works

The published source is a hosted llms.txt endpoint at https://jp-sanctions-production.mk-career-planning.workers.dev/llms.txt. Based on the available description, an MCP-compatible client connects to the hosted Japan MOF Sanctions List Relay MCP server and uses it to ask whether a name is present on Japan’s asset-freeze list.

List-change history is part of the service’s stated behavior. The available material does not explain how history is queried, whether results include dates or versions, how matching is performed, or what data is returned for a match or non-match. Those details should be confirmed from the live endpoint before building a workflow that depends on them.

Tools and capabilities

The documented capabilities are limited to:

• Checking whether a name appears on Japan’s MOF asset-freeze list.
• Retaining history of changes to the list.
• Providing the service through a hosted endpoint.

No individual MCP tool names, parameters, authentication requirements, pagination behavior, or output schema are provided in the supplied material. The phrase “reference only” should be treated as an operational limitation: the Japan MOF Sanctions List Relay MCP server should not be represented as an enforcement or compliance decision system without additional documentation.

Limitations and notes

The repository README is unavailable, so installation instructions, environment variables, licensing, supported MCP clients, and client-specific configuration cannot be confirmed. The listing also does not state whether the hosted endpoint requires credentials or imposes usage limits.

A name-list result alone may not establish that two records refer to the same person or organization. The supplied information does not describe alias handling, transliteration, fuzzy matching, disambiguation, or update timing. Treat results as a reference to the stated list and independently determine any additional review requirements. The service’s retained history may help investigate list changes, but the available material does not specify its retention period or completeness.