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.
Available components
Last scanned (13 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 488 tokens (~122/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +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.
- 15 Oct 26 +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.
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://jp-sanctions-production.mk-career-planning.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mk-career-planning.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 62a608d12f78fd3a8d88d692f2a2cd87fd3 |
| SANs: *.mk-career-planning.workers.dev, mk-career-planning.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jp-sanctions-production.mk-career-planning.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jp-sanctions-production.mk-career-planning.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://jp-sanctions-production.mk-career-planning.workers.dev/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
catalog Catalog: tools, prices and limits ~27
List the tools of this server with prices, data sources, licensing, daily limits and data freshness.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| daily_limits | object | yes | Daily limits of paid calls (calls, usd, timezone) or a misconfiguration notice. |
| fetch_status_values | object | – | – |
| legal | object | yes | – |
| paused | object | yes | Operator pause flags (true = paused). |
| payment | object | yes | – |
| provenance | array | – | Freshness receipts for every upstream source used. |
| server | object | yes | – |
| terms | string | yes | URL of the terms of service. |
| tools | array | yes | Every tool of this server with its price. |
No examples provided.
get_receipt Get receipt of a paid call ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | The receipt_id returned with a paid result ("rcpt_" + 64 hex characters). |
| Name | Type | Req | Description |
|---|---|---|---|
| payment | object | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| receipt_id | string | yes | Receipt id of the settled paid call ("rcpt_" + 64 hex). Use with get_receipt. |
| result | – | yes | The stored result, exactly as returned by the paid call. |
| settled_at | string|null | yes | – |
| terms | string | yes | URL of the terms of service. |
| tool | string | yes | Name of the paid tool that produced the result. |
No examples provided.
sanctions_list_changes MOF asset-freeze list changes since a date ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | ISO 8601 date or date-time with time zone, e.g. 2026-10-01 or 2026-10-01T00:00:00Z |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | – |
| attribution | object | yes | – |
| changes | array | yes | Per-entry differences between list versions observed by this service, oldest first. |
| coverage | object | yes | – |
| history_note | string | yes | – |
| history_window | object | yes | Free history window applied to this answer. |
| legal_notice | string | yes | – |
| not_covered | array | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| query | object | yes | – |
| terms | string | yes | URL of the terms of service. |
| tracking_since | string|null | yes | When this service downloaded its first list version. Nothing before it was observed. |
| truncated | boolean | yes | – |
No examples provided.
sanctions_screen_name Screen a name against the MOF asset-freeze list ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_candidates | integer | – | Maximum number of similar-name candidates to return, 1-25 (default 10) |
| name | string | yes | Name of a person or entity in Latin letters or Japanese (katakana, hiragana or kanji), e.g. 'Vladimir Putin' or 'ウラジーミル・プーチン' |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | – |
| attribution | object | yes | – |
| candidates | array | yes | Similar names. Candidates are not matches. |
| candidates_total | number | yes | – |
| candidates_truncated | boolean | yes | – |
| exact_matches | array | yes | – |
| freshness | – | yes | – |
| history | object | yes | – |
| interpretation | string | yes | – |
| legal_notice | string | yes | – |
| list_version | – | yes | – |
| matching_note | string | yes | – |
| not_covered | array | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| query | object | yes | – |
| status | string | yes | 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 | yes | URL of the terms of service. |
| unknown_reason | string|null | yes | – |
No examples provided.
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.
remote · jp-sanctions-production.mk-career-planning.workers.dev
claude mcp add --transport http mk-career-planning-jp-sanctions 'https://jp-sanctions-production.mk-career-planning.workers.dev/mcp'
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.