Japan Real Estate Transaction Prices (MLIT)
REMOTE · JP-REAL-ESTATE-PRODUCTION.MK-CAREER-PLANNING.WORKERS.DEV
What real estate transaction prices has MLIT published for this Japanese municipality? As published.
Available components
Last scanned (13 hours ago)
Scores higher than 57% 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 Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 595 tokens (~148/item across 4 items; 4 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 Management3
- Stability observed for 1 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.
- 18 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 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-real-estate-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-real-estate-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-real-estate-production.mk-career-planning.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://jp-real-estate-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.
realestate_municipalities Municipality codes in MLIT's list, by prefecture ~121
Which municipality codes and names does MLIT's Real Estate Information Library list for this Japanese prefecture? Give a prefecture code (01-47) or name. Returns the 5-digit municipality codes with Japanese and English names as published by MLIT (XIT002): the join key for realestate_prices_by_municipality and other Japanese public data. Carries the required MLIT credit.
| Name | Type | Req | Description |
|---|---|---|---|
| prefecture | string | yes | Prefecture code 01-47 (e.g. 13) or name (Tokyo or 東京都). |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | – |
| attribution | object | yes | Required credit (MLIT API terms, Article 7; credit_ja is the required wording) and the statement that counts and statistics are computed by MK Career Planning. Keep it when you pass results on. |
| legal_notice | string | yes | – |
| municipalities | array | yes | – |
| prefecture | object | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| retrieved_at | string|null | yes | – |
| source_url | string | yes | – |
| stale | boolean | yes | true = MLIT could not be reached; this is the last list retrieved (see retrieved_at). |
| status | string | yes | found = MLIT's municipality list for the prefecture; unknown = could not be read (see unknown_reason). |
| terms | string | yes | URL of the terms of service. |
| total | number | yes | – |
| unknown_reason | – | yes | – |
No examples provided.
realestate_prices_by_municipality Real estate prices published by MLIT, by municipality ~364
What real estate transaction and contract prices has MLIT (Japan) published for this municipality and quarter? Give a 5-digit municipality code and up to 8 quarters (YYYY-Qn). Per quarter and per classification (never pooled): records_published, no_records_published or unknown with a reason, record counts, min/median/max computed by us (null below 5 values), and a capped sample of records as published. Carries the required MLIT credit. Statistics as published; not an appraisal or advice.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | First quarter, e.g. 2025-Q1 (Q1 = Jan-Mar). Transaction prices start at 2005-Q3, contract prices at 2021-Q1. |
| municipality_code | string | yes | 5-digit Japanese municipality code, e.g. 13101 (Chiyoda, Tokyo). Find codes with realestate_municipalities. Unknown codes are rejected, not guessed. |
| price_classification | string | – | transaction (MLIT 不動産取引価格情報), contract (MLIT 成約価格情報) or both (default). |
| property_type | string | – | Optional filter on MLIT's transaction type: land (宅地(土地)), land_and_building (宅地(土地と建物)), used_condominium (中古マンション等), agricultural_land (農地), forest_land (林地). |
| sample_size | integer | – | Number of published records to include as a sample, 0-50 (default 10). total and truncated tell how many matched. |
| to | string | – | Last quarter, e.g. 2025-Q4 (default: same as from). At most 8 quarters per request. |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | – |
| attribution | object | yes | Required credit (MLIT API terms, Article 7; credit_ja is the required wording) and the statement that counts and statistics are computed by MK Career Planning. Keep it when you pass results on. |
| classification_note | string | yes | Transaction and contract prices are summarised separately; the same deal may appear in both datasets. |
| complete | boolean | yes | true when no quarter is unknown. |
| computed_note | string | yes | – |
| legal_notice | string | yes | – |
| max_quarters_per_request | number | yes | – |
| municipality | – | yes | As published in MLIT's municipality list (XIT002). Null when the list could not be read. |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| quarters | array | yes | – |
| quarters_covered | array | yes | Quarters actually answered (records_published or no_records_published). |
| quarters_requested | array | yes | – |
| query | object | yes | – |
| retrieved_at | string|null | yes | Earliest time the data used here was retrieved from MLIT (cached answers keep their original retrieval time). |
| sample | object | yes | – |
| small_sample_min | number | yes | Statistics with fewer values than this return only n (min, median and max are null). |
| status | string | yes | records_published = at least one quarter has published records matching the query; no_records_published = every quarter was answered and none has matching records; unknown = nothing found and at leas… |
| terms | string | yes | URL of the terms of service. |
No examples provided.
How do I install the Japan Real Estate Transaction Prices (MLIT) MCP server?
Japan Real Estate Transaction Prices (MLIT) is a hosted endpoint at https://jp-real-estate-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-real-estate-production.mk-career-planning.workers.dev
claude mcp add --transport http mk-career-planning-jp-real-estate 'https://jp-real-estate-production.mk-career-planning.workers.dev/mcp'
What is the Japan Real Estate Transaction Prices (MLIT) MCP server?
Japan Real Estate Transaction Prices (MLIT) is an MCP server listed in the public MCP registry as io.github.mk-career-planning/jp-real-estate. What real estate transaction prices has MLIT published for this Japanese municipality? As published. This page covers its hosted endpoint (https://jp-real-estate-production.mk-career-planning.workers.dev/mcp).
Is the Japan Real Estate Transaction Prices (MLIT) MCP server safe to use?
Japan Real Estate Transaction Prices (MLIT) scores 67 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 Real Estate Transaction Prices (MLIT) MCP server expose?
Japan Real Estate Transaction Prices (MLIT) exposes 4 tools: catalog, realestate_prices_by_municipality, realestate_municipalities, get_receipt. Their descriptions and schemas cost roughly 595 tokens of context every time the server is loaded.
Does the Japan Real Estate Transaction Prices (MLIT) MCP server require authentication?
No. We connected to Japan Real Estate Transaction Prices (MLIT) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Japan Real Estate Transaction Prices (MLIT) MCP server still maintained?
Japan Real Estate Transaction Prices (MLIT) 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.