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.
Available components
Last scanned (12 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Finance and Payments
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 Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
- Tool “jp_fsa_registry_lookup” rewrote its description, which is the text the model reads security
- 16 Oct 26 0
- Schema quality: 855 → 1049 ▼ functional
- New tool “fsa_enforcement_by_corporate_number” functional
- 14 Oct 26 +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.
- 13 Oct 26 −1
- Schema quality: 120 → 142 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “fsa_register_changes” functional
- 12 Oct 26 68
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-finance-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-finance-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-finance-production.mk-career-planning.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://jp-finance-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.
fsa_enforcement_by_corporate_number Japan FSA administrative action case list by corporate number ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| corporate_number | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | yes | Rows of the case list stating this corporate number, as published, oldest first. |
| after_as_of | – | yes | The period after the list's as-of date is not covered (unknown). |
| answered_at | string | yes | – |
| attribution | object | yes | – |
| authority | string | yes | – |
| last_observed_at | string|null | yes | – |
| legal_notice | string | yes | – |
| limitations | array | yes | – |
| match_basis | string | yes | – |
| matched_records | array | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| query | object | yes | – |
| registry | string | yes | – |
| registry_name_en | string | yes | – |
| registry_name_ja | string | yes | – |
| scope | object | yes | – |
| source | object | yes | – |
| source_url | string | yes | – |
| status | string | yes | 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 | yes | – |
| status_since | string|null | yes | – |
| terms | string | yes | URL of the terms of service. |
| total | number|null | yes | – |
| tracking_since | string|null | yes | – |
| truncated | boolean | yes | – |
| unknown_reason | string|null | yes | – |
No examples provided.
fsa_register_changes Japan FSA register and warning list changes since a date ~253
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | 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 | – |
| changes | array | yes | Changes observed by this service between list versions, oldest first. Reasons are not published or inferred. |
| checked_until | string|null | yes | Oldest last verification among the lists asked about: changes are recorded up to this time. Use it as the next since. |
| coverage | object | yes | – |
| history_note | string | yes | – |
| history_window | object | yes | Free history window applied to this answer. |
| legal_notice | string | yes | – |
| lists | array | yes | – |
| name_note | string | yes | – |
| official_check | object | 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 | Latest start of continuous change recording among the lists asked about. Nothing before it was compared. |
| truncated | boolean | yes | – |
| versions_observed | array | yes | – |
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.
jp_customs_fx Japan Customs exchange rate lookup ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | Uppercase ISO 4217 alpha-3 code, e.g. USD |
| date | string | yes | Calendar date YYYY-MM-DD (Japan), e.g. 2026-10-07 |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | – |
| dataset_version | string|null | yes | – |
| effective_period | – | yes | Inclusive effective period of the rate (YYYY-MM-DD). |
| notice | string | yes | – |
| query | – | yes | – |
| rate | – | yes | – |
| reason | string | yes | – |
| sources | array | yes | – |
| status | string | yes | valid = published rate found; invalid = malformed input; unknown = could not be confirmed from the checked sources. |
| terms | string | yes | URL of the terms of service. |
No examples provided.
jp_customs_fx_batch Japan Customs exchange rate batch lookup (paid) ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 1 to 50 items {currency, date}; order kept, duplicates answered twice |
Structured output declared, but exposes no named fields.
No examples provided.
jp_fsa_registry_lookup Japan FSA register and warning list check ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | – |
| coverage_complete | boolean | yes | True only when every FSA list was loaded and recently verified. |
| domain_association | – | yes | – |
| entity_resolution | object | yes | How the query ties to a listed entity. A domain alone is always unverified. |
| interpreted | object | yes | – |
| name_candidates | object | yes | Partial name matches, NOT confirmed to be the same entity. |
| not_covered | array | yes | – |
| note | string | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| query | object | yes | – |
| registry_exact_matches | array | yes | Exact matches in FSA registers of licensed businesses, each with its registration type and, where marked in the register, business categories. |
| source_errors | array | yes | – |
| sources_checked | array | yes | – |
| terms | string | yes | URL of the terms of service. |
| warning_exact_matches | array | yes | Exact matches in FSA warnings to unregistered businesses. |
| warning_statement | string | yes | The warning-list result in one statement, with the scope and as-of dates checked. |
No examples provided.
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.
remote · jp-finance-production.mk-career-planning.workers.dev
claude mcp add --transport http mk-career-planning-jp-finance 'https://jp-finance-production.mk-career-planning.workers.dev/mcp'
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.