# Japan Finance Reference Checks (remote · jp-finance-production.mk-career-planning.workers.dev)

Which JPY rate did Japan Customs publish for a date? Is a firm on an FSA list? Hosted. No advice.

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

## Components

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

## Channel facts

- Endpoint: `https://jp-finance-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**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1051 tokens (~150/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 Finance Reference Checks MCP server?

Japan Finance Reference Checks is a hosted endpoint at https://jp-finance-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-finance 'https://jp-finance-production.mk-career-planning.workers.dev/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "mk-career-planning-jp-finance": {
      "type": "http",
      "url": "https://jp-finance-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 69, +1)

- [security] Tool “jp_fsa_registry_lookup” rewrote its description, which is the text the model reads

### 2026-10-16 (score 68, 0)

- [functional regression] Schema quality: 855 → 1049
- [functional] New tool “fsa_enforcement_by_corporate_number”

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

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

### 2026-10-13 (score 67, −1)

- [functional regression] Schema quality: 120 → 142
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “fsa_register_changes”

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

First indexed and scored.

## MCP tools (7)

### `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.

### `jp_customs_fx` (~167 tokens)

Japan Customs exchange rate lookup

Which JPY rate did Japan Customs publish for this currency on this date? Input: ISO 4217 code and YYYY-MM-DD date. Returns status (valid/invalid/unknown), the inclusive effective period, the JPY rate as published with its base units (1 or 100), source URLs, retrieval and verification times and SHA-256 hashes. Dates from 2021-08-15. Unpublished periods and unlisted currencies return unknown. Reference for customs and bookkeeping only; not a market or remittance rate; no tax calculation.

Input parameters:

- `currency` (string, required): Uppercase ISO 4217 alpha-3 code, e.g. USD
- `date` (string, required): Calendar date YYYY-MM-DD (Japan), e.g. 2026-10-07

Output parameters:

- `answered_at` (string)
- `dataset_version` (string|null)
- `effective_period`: Inclusive effective period of the rate (YYYY-MM-DD).
- `notice` (string)
- `query`
- `rate`
- `reason` (string)
- `sources` (array)
- `status` (string): valid = published rate found; invalid = malformed input; unknown = could not be confirmed from the checked sources.
- `terms` (string): URL of the terms of service.

### `jp_fsa_registry_lookup` (~188 tokens)

Japan FSA register and warning list check

Is this business (name, registration or 13-digit corporate number) on a Japan FSA register or warning list? Exact match (optional domain) against FSA registers (financial instruments, crypto-asset exchange, electronic payment instruments, funds transfer, money lending) and warnings to unregistered businesses. Returns matches with registration type, entity tie (domain alone: unverified), name candidates and as-of dates. Stated scope only; no warning match is not proof none exists. No advice.

Input parameters:

- `domain` (string): Optional domain or URL, e.g. example.com
- `name` (string): Business name as written, e.g. 株式会社SBI証券 or Bybit Fintech Limited
- `number` (string): Registration number (e.g. 関東財務局長(金商)第44号) or 13-digit corporate number

Output parameters:

- `answered_at` (string)
- `coverage_complete` (boolean): True only when every FSA list was loaded and recently verified.
- `domain_association`
- `entity_resolution` (object): How the query ties to a listed entity. A domain alone is always unverified.
- `interpreted` (object)
- `name_candidates` (object): Partial name matches, NOT confirmed to be the same entity.
- `not_covered` (array)
- `note` (string)
- `provenance` (array): Freshness receipts for every upstream source used.
- `query` (object)
- `registry_exact_matches` (array): Exact matches in FSA registers of licensed businesses, each with its registration type and, where marked in the register, business categories.
- `source_errors` (array)
- `sources_checked` (array)
- `terms` (string): URL of the terms of service.
- `warning_exact_matches` (array): Exact matches in FSA warnings to unregistered businesses.
- `warning_statement` (string): The warning-list result in one statement, with the scope and as-of dates checked.

### `fsa_register_changes` (~253 tokens)

Japan FSA register and warning list changes since a date

Which entries were added to, dropped from, changed in or returned to Japan FSA registers and warning lists since a date? From this service's own record of list versions (the FSA publishes only current lists). Each change has the list, registration number, name as published (personal names withheld), before/after fields, observed_at and the list as-of date. Reasons are not published or inferred. History starts at tracking_since; free window: last 30 days.

Input parameters:

- `change_type` (string): Optional filter: added, no_longer_listed, details_changed or relisted
- `limit` (integer): Maximum number of changes, 1-500 (default 100)
- `list` (string): Optional: one list id (fib, cae, epi, fts, ml, w_fib_dom, w_fib_ovs, w_fib_qii, w_cae_dom, w_cae_ovs) or registers / warnings; default all lists
- `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)
- `changes` (array): Changes observed by this service between list versions, oldest first. Reasons are not published or inferred.
- `checked_until` (string|null): Oldest last verification among the lists asked about: changes are recorded up to this time. Use it as the next since.
- `coverage` (object)
- `history_note` (string)
- `history_window` (object): Free history window applied to this answer.
- `legal_notice` (string)
- `lists` (array)
- `name_note` (string)
- `official_check` (object)
- `provenance` (array): Freshness receipts for every upstream source used.
- `query` (object)
- `terms` (string): URL of the terms of service.
- `tracking_since` (string|null): Latest start of continuous change recording among the lists asked about. Nothing before it was compared.
- `truncated` (boolean)
- `versions_observed` (array)

### `fsa_enforcement_by_corporate_number` (~194 tokens)

Japan FSA administrative action case list by corporate number

Which rows of the Japan FSA case list of adverse administrative actions (business improvement or suspension orders and similar, by the FSA and Local Finance Bureaus, fiscal 2002 to the list's as-of date) state this 13-digit corporate number? Rows as published: date, action type, legal basis, business type, lifted flag, with the list version, SHA-256 and the scope of what was checked. Zero rows is not_found_in_checked_records with that scope; after the as-of date is unknown. No name search.

Input parameters:

- `corporate_number` (string, required): 13-digit Japanese corporate number (houjin bangou), e.g. 3010401049814. The check digit is verified.
- `since` (string): Optional: only actions published on or after this date (YYYY-MM-DD). A date after the list's as-of date returns unknown.

Output parameters:

- `actions` (array): Rows of the case list stating this corporate number, as published, oldest first.
- `after_as_of`: The period after the list's as-of date is not covered (unknown).
- `answered_at` (string)
- `attribution` (object)
- `authority` (string)
- `last_observed_at` (string|null)
- `legal_notice` (string)
- `limitations` (array)
- `match_basis` (string)
- `matched_records` (array)
- `provenance` (array): Freshness receipts for every upstream source used.
- `query` (object)
- `registry` (string)
- `registry_name_en` (string)
- `registry_name_ja` (string)
- `scope` (object)
- `source` (object)
- `source_url` (string)
- `status` (string): listed = rows of the case list state this corporate number; not_found_in_checked_records = none in the checked version and scope; unknown = not loaded, not confirmed recently or period after the as-o…
- `status_as_of` (string|null)
- `status_since` (string|null)
- `terms` (string): URL of the terms of service.
- `total` (number|null)
- `tracking_since` (string|null)
- `truncated` (boolean)
- `unknown_reason` (string|null)

### `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.

### `jp_customs_fx_batch` (~139 tokens)

Japan Customs exchange rate batch lookup (paid)

Which JPY rates did Japan Customs publish for these 1-50 currency/date pairs? One call returns ordered per-item status, effective periods, JPY rates as published with base units (1 or 100), source URLs, retrieval and verification times and hashes, read from one dataset snapshot. Dates from 2021-08-15. Unpublished periods and unlisted currencies return unknown. Not charged if no item can be answered. No date selection, tax calculation, market or remittance rates, or forecasts.

Input parameters:

- `items` (array, required): 1 to 50 items {currency, date}; order kept, duplicates answered twice

## Diagnostics

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

## Score history

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

## Common questions

### What is the Japan Finance Reference Checks MCP server?

Japan Finance Reference Checks is an MCP server listed in the public MCP registry as io.github.mk-career-planning/jp-finance. Which JPY rate did Japan Customs publish for a date? Is a firm on an FSA list? Hosted. No advice. This page covers its hosted endpoint (https://jp-finance-production.mk-career-planning.workers.dev/mcp).

### Is the Japan Finance Reference Checks MCP server safe to use?

Japan Finance Reference Checks scores 69 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 Finance Reference Checks MCP server expose?

Japan Finance Reference Checks exposes 7 tools: catalog, jp_customs_fx, jp_fsa_registry_lookup, fsa_register_changes, fsa_enforcement_by_corporate_number, and 2 more. Their descriptions and schemas cost roughly 1,051 tokens of context every time the server is loaded.

### Does the Japan Finance Reference Checks MCP server require authentication?

No. We connected to Japan Finance Reference Checks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Japan Finance Reference Checks MCP server still maintained?

Japan Finance Reference Checks 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-finance-production.mk-career-planning.workers.dev/mcp
- Website: https://jp-finance-production.mk-career-planning.workers.dev/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/mk-career-planning-jp-finance/jp-finance-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/mk-career-planning-jp-finance/jp-finance-production.json
- HTML version of this page: https://verifymcp.io/servers/mk-career-planning-jp-finance/jp-finance-production