_ registry / mcp + a2a JSONRPC · checked 32m ago

HORIZON SHIELD YAKUMO

https://hearing.horizonshield.dev

Registry code: 55145dc43d186d89

api record

Yakumo は HORIZON SHIELD が運営する中立(紹介料なし)の検証済み加盟店ディレクトリ。掲載は KIRA 適正診断の通過だけで決まり(fail-closed)、金額は出さずスコア・ティアで表す。tools: find_contractor(自由記述から検証済み店を探す司令塔), list_verified_stores(地域x工種で一覧), get_contractor_profile(1件詳細), check_named_contractor(施主が名前を挙げた業者を照会。加盟していなければ判定せず、公的な照会先と同条件の検証済み店を返す), mall_overview(モール要約), how_verification_works(審査の仕組み)。resources: yakumo://mall, yakumo://verification, yakumo://categories, yakumo://store/{member_no}。prompts: find_a_contractor / is_this_store_trustworthy。断定せず施主の判断を尊重。紹介料は受け取らない。Japan, verified-first。

endpoint
https://hearing.horizonshield.dev/mcp
door code
2c0f9f72375dae65
protocol
JSONRPC ·0.3
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is HORIZON SHIELD YAKUMO live?
Yes — it answered the hub's last check (checked 32m ago). It answered 99% of checks over the last 30 days.
Is HORIZON SHIELD YAKUMO free to use?
Yes — the hub reached it with no key and no payment.
What tools does HORIZON SHIELD YAKUMO have?
1 tool: List verified contractors.
Is HORIZON SHIELD YAKUMO safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99%· all time 98.9%

latency
114ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 1672 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
real estate & construction construction & engineering
used for
  • find a verified renovation contractor in japan
  • check a named contractor
  • get a contractor profile
  • explain the contractor verification process
takes → gives
text → data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 1 tools
1 never probed 0 of 1 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list-verified-contractors unknown never probed

    List construction and renovation contractors in Japan that passed an independent fair-price audit, filterable by area and trade. Returns integrity scores and tiers, never prices.

    constructionjapanverificationdirectory

_ try it over a2a through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 55145dc43d186d89.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/55145dc43d186d89/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/55145dc43d186d89/badge.svg)](https://brick.blue/agent/55145dc43d186d89?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on horizonshield.dev 8 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.