MCP.Market

HORIZON SHIELD YAKUMO (verified contractor directory) MCP server

online · 100% uptime
by ogasurfproject-jpg·io.github.ogasurfproject-jpg/hs-hearing·v2.3.1·2 stars
No reviews yet

Neutral, verification-gated MCP directory of Japan construction contractors (KIRA-audited).

A88/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

2 stars

Reviews

Write one

Nobody has reviewed HORIZON SHIELD YAKUMO (verified contractor directory) yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

HORIZON SHIELD YAKUMO (verified contractor directory) tools (6)

write = sends, deletes, buys or posts
  • check_named_contractorFree

    施主が名前を挙げた業者について答える。Yakumoの加盟店ならその測定結果を返す。加盟していない場合、その会社の良し悪しは一切判定せず、『Yakumoは測っていない』という事実だけを返し、施主が自分で確かめられる公的な照会先(国土交通省の建設業者検索・国民生活センター・住まいるダイヤル)と、同条件の検証済み加盟店を返す。掲載が無いことはその会社への評価ではない。金額は返さない。紹介料なし。Japan only。

  • find_contractorFree

    施主の相談文(自由記述)から Yakumo の検証済み加盟店を探す司令塔。need(例:『愛知県で外壁塗装できる信頼できる業者』)を渡すと地域と工種を推定し、検証を通過した店を返す。該当が無ければ相場(souba)や無料の第三者チェック(EHN)への導線を返す。金額は返さない(スコア・ティアのみ)。紹介料なし・verified-first・Japan only。

  • get_contractor_profileFree

    Yakumo の加盟店1件の検証済みプロフィールを返す。member_no(例 No.001)で指定。会社名・地域・対応工種・適正度スコア・誠実度ティア・検証状態・プロフィールURLを返す。金額は含まない。検証が済んでいない店は verification:'pending' を返す(スコアは出さない=fail-closed)。

  • how_verification_worksFree

    Yakumo の掲載審査(KIRA適正診断)がどう機能するかを返す。適正価格の検証・過剰請求の赤旗検出・適正度スコアと誠実度ティア・再計算できる署名レシート(SHA-256)・掲載後の継続監視・fail-closed(通らない店は施主向けに一切出さない)・中立(紹介料なし)。施主が『検証済み』の意味を理解するための説明。

  • list_verified_storesFree

    Yakumo モールで検証を通過した加盟店(工務店・リフォーム店)を一覧する。適正価格の検証と過剰請求チェック(KIRA)を通過した店だけが返る。area(地名)や work(工種)で絞り込める。返り値は member_no / 会社名 / 地域 / 対応工種 / 適正度スコア / 誠実度ティア / プロフィールURL。金額は含まない(スコアとティアのみ)。検証手続き中の店は verification:'pending' として区別される。Japan only.

  • mall_overviewFree

    Yakumo モール全体の要約を返す。検証済み加盟店の数・対応工種カテゴリ・地域・検証の仕組みの要点・主要リンク(モール/加盟/相場/実例ボード)。AIが Yakumo というモール/MCP を一言で説明するための入口。金額は含まない。

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 509ms20/20
  • Tool poisoning6 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How HORIZON SHIELD YAKUMO (verified contractor directory) compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,243 servers
Tools
6
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
55 ms
faster than 92% of 30,027 servers
GitHub stars
2
more than 75% of 28,706 servers

What its tools let an agent do: 6 read

Install HORIZON SHIELD YAKUMO (verified contractor directory) in Claude Code, Cursor or VS Code

claude mcp add --transport http hs-hearing https://hearing.horizonshield.dev/mcp
Add to Cursor

What the publisher says

From the HORIZON SHIELD YAKUMO (verified contractor directory) repository's README, as published. We do not edit it. Read it on GitHub

🛡️ HORIZON SHIELD

Verifiable construction estimate auditing for AI agents

Don't trust the estimate. Verify it.

An MCP server that lets AI agents check whether a Japanese construction or renovation estimate is fair, against open data, and returns a result anyone can verify against Bitcoin (OpenTimestamps). No account, no key.

NENRIN: tree rings for AI facing services

A tree adds one ring a year. Nobody can paint one in afterwards. NENRIN gives that property to software services.

In one thirty day window, measured 2026-08-17, this server appeared in 93,983 AI search results. How many of those became a call from outside, we cannot say. The usage counter deliberately stores no IP addresses, so it cannot separate our own automated checks from external traffic. An earlier version of this paragraph said the answer was 0. This instrument cannot establish that, so the claim is withdrawn here rather than quietly deleted. Discovery is solved. Choice is not. An agent picking between 90,000 servers can only read what each vendor wrote about itself. NENRIN adds the missing layer: records of conduct that the vendor did not author and cannot delete.

How it works, in three lines:

  1. Open witnessing. Anyone can measure any endpoint and submit the walk to the public ledger under their own name and vantage. The operator holds no veto: acceptance is mechanical schema checking, and the code that enforces this is in this repository.
  2. Discrepancies are the product. When two witnesses report incompatible observations of the same target, the disagreement itself becomes a permanent, citable record. The founding one is real: NENRINDISCREPANCY0001, two honest witnesses, one target, both correct.
  3. Rings. Each month the accepted records bundle into a ring that carries the hash of the previous ring, timestamped to Bitcoin. Eighteen months of rings cannot be created in an afternoon, by anyone, including us.

The specification is anchored on the public ledger as entry 19 (sha256 9ccba2e325fd2a555fcdb2dec519b8c6bf7a669064674846aea98ecfff824e3d): NENRINSPECv1.md. It names its own prior art (Certificate Transparency, Rekor, in-toto, SLSA, OpenTimestamps), states exactly which combination is claimed as new, and invites refutation into the same ledger.

The witness intake is live. Start here:

curl -s https://ledger.horizonshield.dev/witness

We are the first test subject under our own rules. The ledger keeps the record of our gate failing its own test, and the full 522 incident that started all of this. Unflattering records stay.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

HORIZON SHIELD YAKUMO (verified contractor directory): common questions

Is HORIZON SHIELD YAKUMO (verified contractor directory) MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the HORIZON SHIELD YAKUMO (verified contractor directory) safety report
How do I install HORIZON SHIELD YAKUMO (verified contractor directory)?
It runs remotely at hearing.horizonshield.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does HORIZON SHIELD YAKUMO (verified contractor directory) need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is HORIZON SHIELD YAKUMO (verified contractor directory) maintained?
The last commit was 20 days ago (2026-10-16). The latest release is v2.3.1.
Is HORIZON SHIELD YAKUMO (verified contractor directory) up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of HORIZON SHIELD YAKUMO (verified contractor directory)?
Servers from other publishers that do the same job: SSH — policy-gated remote access MCP server.
How does HORIZON SHIELD YAKUMO (verified contractor directory) compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,243 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to HORIZON SHIELD YAKUMO (verified contractor directory)

Same job from other publishers: the closest match first, then the best rated.

More from ogasurfproject-jpg →