# Japan MOF Sanctions List Relay (remote · jp-sanctions-production.mk-career-planning.workers.dev)

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

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `jp-sanctions-production.mk-career-planning.workers.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/mk-career-planning-jp-sanctions/jp-sanctions-production.md), [page](https://verifymcp.io/servers/mk-career-planning-jp-sanctions/jp-sanctions-production)

## Channel facts

- Endpoint: `https://jp-sanctions-production.mk-career-planning.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 488 tokens (~122/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Japan MOF Sanctions List Relay MCP server?

Japan MOF Sanctions List Relay is a hosted endpoint at https://jp-sanctions-production.mk-career-planning.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http mk-career-planning-jp-sanctions 'https://jp-sanctions-production.mk-career-planning.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mk-career-planning-jp-sanctions": {
      "url": "https://jp-sanctions-production.mk-career-planning.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mk-career-planning-jp-sanctions": {
      "type": "http",
      "url": "https://jp-sanctions-production.mk-career-planning.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mk-career-planning-jp-sanctions]
url = "https://jp-sanctions-production.mk-career-planning.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mk-career-planning-jp-sanctions": {
      "type": "remote",
      "url": "https://jp-sanctions-production.mk-career-planning.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mk-career-planning-jp-sanctions --url 'https://jp-sanctions-production.mk-career-planning.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mk-career-planning-jp-sanctions:
    url: "https://jp-sanctions-production.mk-career-planning.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mk-career-planning-jp-sanctions": {
      "Transport": "http",
      "Url": "https://jp-sanctions-production.mk-career-planning.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mk-career-planning-jp-sanctions -t streamable-http -u 'https://jp-sanctions-production.mk-career-planning.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mk-career-planning-jp-sanctions": {
      "type": "http",
      "url": "https://jp-sanctions-production.mk-career-planning.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 67)

First indexed and scored.

## MCP tools (4)

### `catalog` (~27 tokens)

Catalog: tools, prices and limits

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

Output parameters:

- `daily_limits` (object): Daily limits of paid calls (calls, usd, timezone) or a misconfiguration notice.
- `fetch_status_values` (object)
- `legal` (object)
- `paused` (object): Operator pause flags (true = paused).
- `payment` (object)
- `provenance` (array): Freshness receipts for every upstream source used.
- `server` (object)
- `terms` (string): URL of the terms of service.
- `tools` (array): Every tool of this server with its price.

### `sanctions_screen_name` (~171 tokens)

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.

Input parameters:

- `max_candidates` (integer): Maximum number of similar-name candidates to return, 1-25 (default 10)
- `name` (string, required): Name of a person or entity in Latin letters or Japanese (katakana, hiragana or kanji), e.g. 'Vladimir Putin' or 'ウラジーミル・プーチン'

Output parameters:

- `answered_at` (string)
- `attribution` (object)
- `candidates` (array): Similar names. Candidates are not matches.
- `candidates_total` (number)
- `candidates_truncated` (boolean)
- `exact_matches` (array)
- `freshness`
- `history` (object)
- `interpretation` (string)
- `legal_notice` (string)
- `list_version`
- `matching_note` (string)
- `not_covered` (array)
- `provenance` (array): Freshness receipts for every upstream source used.
- `query` (object)
- `status` (string): exact_match = equal after normalization to a listed name, alias or former name (identity not confirmed); candidates = similar names only, NOT matches; no_match_in_checked_list = not found in the list…
- `terms` (string): URL of the terms of service.
- `unknown_reason` (string|null)

### `sanctions_list_changes` (~207 tokens)

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.

Input parameters:

- `change_type` (string): Optional filter: added, removed or modified
- `entry_id` (string): Optional filter: MOF list number, e.g. 029-000001
- `limit` (integer): Maximum number of changes, 1-200 (default 100)
- `since` (string, required): ISO 8601 date or date-time with time zone, e.g. 2026-10-01 or 2026-10-01T00:00:00Z

Output parameters:

- `answered_at` (string)
- `attribution` (object)
- `changes` (array): Per-entry differences between list versions observed by this service, oldest first.
- `coverage` (object)
- `history_note` (string)
- `history_window` (object): Free history window applied to this answer.
- `legal_notice` (string)
- `not_covered` (array)
- `provenance` (array): Freshness receipts for every upstream source used.
- `query` (object)
- `terms` (string): URL of the terms of service.
- `tracking_since` (string|null): When this service downloaded its first list version. Nothing before it was observed.
- `truncated` (boolean)

### `get_receipt` (~83 tokens)

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.

Input parameters:

- `receipt_id` (string, required): The receipt_id returned with a paid result ("rcpt_" + 64 hex characters).

Output parameters:

- `payment` (object)
- `provenance` (array): Freshness receipts for every upstream source used.
- `receipt_id` (string): Receipt id of the settled paid call ("rcpt_" + 64 hex). Use with get_receipt.
- `result`: The stored result, exactly as returned by the paid call.
- `settled_at` (string|null)
- `terms` (string): URL of the terms of service.
- `tool` (string): Name of the paid tool that produced the result.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mk-career-planning-jp-sanctions/jp-sanctions-production#diagnostics

## Score history

- 2026-10-18: 70
- 2026-10-17: 70
- 2026-10-16: 69
- 2026-10-15: 69
- 2026-10-14: 68
- 2026-10-13: 68
- 2026-10-12: 67

## Common questions

### What is the Japan MOF Sanctions List Relay MCP server?

Japan MOF Sanctions List Relay is an MCP server listed in the public MCP registry as io.github.mk-career-planning/jp-sanctions. Is this name on Japan's MOF asset-freeze list? Hosted, list-change history kept. Reference only. This page covers its hosted endpoint (https://jp-sanctions-production.mk-career-planning.workers.dev/mcp).

### Is the Japan MOF Sanctions List Relay MCP server safe to use?

Japan MOF Sanctions List Relay scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Japan MOF Sanctions List Relay MCP server expose?

Japan MOF Sanctions List Relay exposes 4 tools: catalog, sanctions_screen_name, sanctions_list_changes, get_receipt. Their descriptions and schemas cost roughly 488 tokens of context every time the server is loaded.

### Does the Japan MOF Sanctions List Relay MCP server require authentication?

No. We connected to Japan MOF Sanctions List Relay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Japan MOF Sanctions List Relay MCP server still maintained?

Japan MOF Sanctions List Relay is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://jp-sanctions-production.mk-career-planning.workers.dev/mcp
- Website: https://jp-sanctions-production.mk-career-planning.workers.dev/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/mk-career-planning-jp-sanctions/jp-sanctions-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/mk-career-planning-jp-sanctions/jp-sanctions-production.json
- HTML version of this page: https://verifymcp.io/servers/mk-career-planning-jp-sanctions/jp-sanctions-production