HORIZON SHIELD YAKUMO (verified contractor directory)
REMOTE · HEARING.HORIZONSHIELD.DEV
Neutral, verification-gated MCP directory of Japan construction contractors (KIRA-audited).
Available components
Last scanned (9 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Maps and Location
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 Security71
- 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 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1340 tokens (~148/item across 9 items; 6 tools + 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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.
- 14 Oct 26 0
- Server version: 2.3.1 → 2.3.2-rmw-20261013 functional
- 28 Sept 26 +3
- 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
- 8 Sept 26 0
- Stability: 0.97 → pass security
- 4 Sept 26 0
- Server version: 2.3.0 → 2.3.1 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
- 19 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 131 → 148 ▼ functional
- Server version: 2.2.0 → 2.3.0 functional
- New tool “check_named_contractor” functional
- 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
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 24 Oct 2026 · Probed https://hearing.horizonshield.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=horizonshield.dev | CN=WE1,O=Google Trust Services,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ec78a88f90aee500133fc3a9a556a9b1 |
| SANs: horizonshield.dev, *.horizonshield.dev | ||||||
| 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 secure
Validation of hearing.horizonshield.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| horizonshield.dev. | present | 2371 | 13 | Verified |
| hearing.horizonshield.dev. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hearing.horizonshield.dev/mcp | Verified | 200 | |
| http (plaintext) | http://hearing.horizonshield.dev/mcp | Inconclusive | 405 |
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 →
check_named_contractor 名指しの業者を照会 ~242
施主が名前を挙げた業者について答える。Yakumoの加盟店ならその測定結果を返す。加盟していない場合、その会社の良し悪しは一切判定せず、『Yakumoは測っていない』という事実だけを返し、施主が自分で確かめられる公的な照会先(国土交通省の建設業者検索・国民生活センター・住まいるダイヤル)と、同条件の検証済み加盟店を返す。掲載が無いことはその会社への評価ではない。金額は返さない。紹介料なし。Japan only。
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | (任意)地域。代わりの検証済み店を探すのに使う |
| company | string | yes | 施主が名前を挙げた業者名(日本語) |
| work | string | – | (任意)工種。代わりの検証済み店を探すのに使う |
| Name | Type | Req | Description |
|---|---|---|---|
| pending_count | number | – | – |
| roster_read | boolean | – | true = the contractor roster was read successfully; any counts below are real facts about the roster. false = the roster could NOT be read, and this response makes no claim about how many contractors… |
| roster_source | string | – | – |
| verified_count | number | – | – |
No examples provided.
find_contractor 検証済みの職人を探す(司令塔) ~181
施主の相談文(自由記述)から Yakumo の検証済み加盟店を探す司令塔。need(例:『愛知県で外壁塗装できる信頼できる業者』)を渡すと地域と工種を推定し、検証を通過した店を返す。該当が無ければ相場(souba)や無料の第三者チェック(EHN)への導線を返す。金額は返さない(スコア・ティアのみ)。紹介料なし・verified-first・Japan only。
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | yes | 探している内容(日本語自由記述)。例: 神奈川で屋根の雨漏り修理、長久手で内装リフォーム |
| Name | Type | Req | Description |
|---|---|---|---|
| pending_count | number | – | – |
| roster_read | boolean | – | true = the contractor roster was read successfully; any counts below are real facts about the roster. false = the roster could NOT be read, and this response makes no claim about how many contractors… |
| roster_source | string | – | – |
| verified_count | number | – | – |
No examples provided.
get_contractor_profile 加盟店プロフィール取得 ~127
Yakumo の加盟店1件の検証済みプロフィールを返す。member_no(例 No.001)で指定。会社名・地域・対応工種・適正度スコア・誠実度ティア・検証状態・プロフィールURLを返す。金額は含まない。検証が済んでいない店は verification:'pending' を返す(スコアは出さない=fail-closed)。
| Name | Type | Req | Description |
|---|---|---|---|
| member_no | string | yes | 加盟店番号(例: No.001) |
| Name | Type | Req | Description |
|---|---|---|---|
| pending_count | number | – | – |
| roster_read | boolean | – | true = the contractor roster was read successfully; any counts below are real facts about the roster. false = the roster could NOT be read, and this response makes no claim about how many contractors… |
| roster_source | string | – | – |
| verified_count | number | – | – |
No examples provided.
how_verification_works 検証の仕組み ~138
Yakumo の掲載審査(KIRA適正診断)がどう機能するかを返す。適正価格の検証・過剰請求の赤旗検出・適正度スコアと誠実度ティア・再計算できる署名レシート(SHA-256)・掲載後の継続監視・fail-closed(通らない店は施主向けに一切出さない)・中立(紹介料なし)。施主が『検証済み』の意味を理解するための説明。
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| pending_count | number | – | – |
| roster_read | boolean | – | true = the contractor roster was read successfully; any counts below are real facts about the roster. false = the roster could NOT be read, and this response makes no claim about how many contractors… |
| roster_source | string | – | – |
| verified_count | number | – | – |
No examples provided.
list_verified_stores 検証済み加盟店の一覧 ~225
Yakumo モールで検証を通過した加盟店(工務店・リフォーム店)を一覧する。適正価格の検証と過剰請求チェック(KIRA)を通過した店だけが返る。area(地名)や work(工種)で絞り込める。返り値は member_no / 会社名 / 地域 / 対応工種 / 適正度スコア / 誠実度ティア / プロフィールURL。金額は含まない(スコアとティアのみ)。検証手続き中の店は verification:'pending' として区別される。Japan only.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | 地名で絞り込み(例: 愛知県, 長久手市)。省略で全件。 |
| work | string | – | 工種で絞り込み(例: 外壁塗装, 屋根, 内装)。省略で全件。 |
| Name | Type | Req | Description |
|---|---|---|---|
| pending_count | number | – | – |
| roster_read | boolean | – | true = the contractor roster was read successfully; any counts below are real facts about the roster. false = the roster could NOT be read, and this response makes no claim about how many contractors… |
| roster_source | string | – | – |
| verified_count | number | – | – |
No examples provided.
mall_overview モール概要 ~91
Yakumo モール全体の要約を返す。検証済み加盟店の数・対応工種カテゴリ・地域・検証の仕組みの要点・主要リンク(モール/加盟/相場/実例ボード)。AIが Yakumo というモール/MCP を一言で説明するための入口。金額は含まない。
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| pending_count | number | – | – |
| roster_read | boolean | – | true = the contractor roster was read successfully; any counts below are real facts about the roster. false = the roster could NOT be read, and this response makes no claim about how many contractors… |
| roster_source | string | – | – |
| verified_count | number | – | – |
No examples provided.
How do I install the HORIZON SHIELD YAKUMO (verified contractor directory) MCP server?
HORIZON SHIELD YAKUMO (verified contractor directory) is a hosted endpoint at https://hearing.horizonshield.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 · hearing.horizonshield.dev
claude mcp add --transport http ogasurfproject-jpg-hs-hearing 'https://hearing.horizonshield.dev/mcp'
What is the HORIZON SHIELD YAKUMO (verified contractor directory) MCP server?
HORIZON SHIELD YAKUMO (verified contractor directory) is an MCP server listed in the public MCP registry as io.github.ogasurfproject-jpg/hs-hearing. Neutral, verification-gated MCP directory of Japan construction contractors (KIRA-audited). This page covers its hosted endpoint (https://hearing.horizonshield.dev/mcp).
Is the HORIZON SHIELD YAKUMO (verified contractor directory) MCP server safe to use?
HORIZON SHIELD YAKUMO (verified contractor directory) scores 85 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 HORIZON SHIELD YAKUMO (verified contractor directory) MCP server expose?
HORIZON SHIELD YAKUMO (verified contractor directory) exposes 6 tools: list_verified_stores, get_contractor_profile, find_contractor, mall_overview, how_verification_works, check_named_contractor. Their descriptions and schemas cost roughly 1,004 tokens of context every time the server is loaded.
Does the HORIZON SHIELD YAKUMO (verified contractor directory) MCP server require authentication?
No. We connected to HORIZON SHIELD YAKUMO (verified contractor directory) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HORIZON SHIELD YAKUMO (verified contractor directory) MCP server still maintained?
HORIZON SHIELD YAKUMO (verified contractor directory) is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.