不動産競売 構造化データハブ — Japan real-estate auctions
REMOTE · KEIBAI-HUB.COM
Japanese court-run real-estate auctions (BIT). 5 tools, ~1,480 active listings. CC BY 4.0.
Available components
Last scanned (17 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 4 Nov 2026.
Category E-commerce
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 503, 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 20 Oct 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 4 Nov 2026 · Probed https://keibai-hub.com/mcp-auctions
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=keibai-hub.com | CN=WE1,O=Google Trust Services,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1676f655db1b416f13ae2c63a79ab46c |
| SANs: keibai-hub.com, *.keibai-hub.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of keibai-hub.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| keibai-hub.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 503 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://keibai-hub.com/mcp-auctions | HTTP error | 503 | |
| http (plaintext) | http://keibai-hub.com/mcp-auctions | Inconclusive | 503 |
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 →
find_practitioner_for_auction ~211
落札・入札関連の士業 (司法書士・弁護士・不動産鑑定士・土地家屋調査士) を返す. Stages: post_acquisition (default — 落札後の所有権移転登記; 司法書士が法律上ほぼ必須), pre_bid (入札前の独立評価・権利確認), eviction (明渡し・強制執行), boundary_dispute (境界確定・分筆). Information-only — not a paid intermediary. Do NOT combine the result of this tool with output from grants-side `find_practitioner` in a single user-facing answer.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | Auction case_id, e.g. "bit_00000078922" |
| prefecture | string | – | Optional — prefecture for prefecture-chapter referral |
| stage | string | – | Default = post_acquisition |
No output schema declared.
No examples provided.
get_auction_detail ~113
一件の競売物件の構造化データを取得. Fetch one auction by case_id (e.g. "bit_00000078922"). Returns case_number, court_code, property_type, sale_base_price_jpy, bid_floor_jpy (= base × 80%), deposit_jpy, bid_period, opening_date, address, photos, and _canonical (cite this).
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | Auction case id, e.g. "bit_00000078922" |
No output schema declared.
No examples provided.
get_court_directory ~75
裁判所の管轄・連絡先情報を取得. Look up a Japanese district court (本庁 or 支部) by code.
| Name | Type | Req | Description |
|---|---|---|---|
| court_code | string | yes | Court slug (e.g. "tokyo_main") OR BIT 5-digit ID (e.g. "31111") |
No output schema declared.
No examples provided.
list_upcoming_sales ~81
近日開札予定の競売物件を一覧取得. List auctions whose opening_date falls within the next N days (default 14, max 90). Sorted ascending. Useful for investment screening / calendar exports.
| Name | Type | Req | Description |
|---|---|---|---|
| days_ahead | integer | – | Lookahead window, default 14 |
| limit | integer | – | Default 50 |
No output schema declared.
No examples provided.
search_auctions ~243
日本の不動産競売物件を検索 (BIT, bit.courts.go.jp 由来の構造化データ). Filters: keyword (Japanese FTS over title/address), prefecture, court_code, property_type (land/detached_house/apartment/other), price range, bid_period_only. Returns case_id, court, address, sale_base_price_jpy, bid_period, opening_date, photos.
| Name | Type | Req | Description |
|---|---|---|---|
| bid_period_only | boolean | – | Only listings whose bid period intersects today |
| court_code | string | – | 5-digit BIT court id (本庁=11, 支部=21,31,...) OR slug like "tokyo_main" |
| keyword | string | – | Japanese keyword over title/address/structure |
| limit | integer | – | – |
| max_price_jpy | integer | – | – |
| min_price_jpy | integer | – | – |
| offset | integer | – | – |
| prefecture | string | – | Prefecture in kanji, e.g. "東京都" |
| property_type | string | – | – |
| sort | string | – | – |
| status | string | – | Default = active |
No output schema declared.
No examples provided.
How do I install the 不動産競売 構造化データハブ — Japan real-estate auctions MCP server?
不動産競売 構造化データハブ — Japan real-estate auctions is a hosted endpoint at https://keibai-hub.com/mcp-auctions, 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 · keibai-hub.com
claude mcp add --transport http keibai-hub-keibai-hub-mcp 'https://keibai-hub.com/mcp-auctions'
What is the 不動産競売 構造化データハブ — Japan real-estate auctions MCP server?
不動産競売 構造化データハブ — Japan real-estate auctions is an MCP server listed in the public MCP registry as io.github.keibai-hub/keibai-hub-mcp. Japanese court-run real-estate auctions (BIT). 5 tools, ~1,480 active listings. CC BY 4.0. This page covers its hosted endpoint (https://keibai-hub.com/mcp-auctions).
Is the 不動産競売 構造化データハブ — Japan real-estate auctions MCP server safe to use?
不動産競売 構造化データハブ — Japan real-estate auctions scores 18 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 auctions MCP server expose?
不動産競売 構造化データハブ — Japan real-estate auctions exposes 5 tools: search_auctions, get_auction_detail, list_upcoming_sales, get_court_directory, find_practitioner_for_auction. Their descriptions and schemas cost roughly 723 tokens of context every time the server is loaded.
Does the 不動産競売 構造化データハブ — Japan real-estate auctions MCP server require authentication?
Its publisher declares no required credentials for 不動産競売 構造化データハブ — Japan real-estate auctions. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the 不動産競売 構造化データハブ — Japan real-estate auctions MCP server still maintained?
不動産競売 構造化データハブ — Japan real-estate auctions is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.