_ registry / mcp + a2a streamable-http · checked 2h ago

hs-partner-001-mcp

https://p001.horizonshield.dev

Registry code: 02e2eb9b2fd0a0dd

api record

Verified profile of Reform Shokunin Co., Ltd., a Yakumo member renovation contractor in Aichi.

from a public catalogue that lists it, not from the operator

endpoint
https://p001.horizonshield.dev/mcp
door code
1e00ac3724092093
protocol
streamable-http ·2025-06-18
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 hs-partner-001-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is hs-partner-001-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does hs-partner-001-mcp have?
1 tool: get_partner_profile.
Is hs-partner-001-mcp 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%

90 days 99%· all time 98.9%

latency
113ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 829 checks · signed record
  • down → live
  • degraded → down· fetch failed
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
_ what it is for
topic
real estate & construction construction & engineering
used for
  • get a verified renovation contractor profile
  • check a contractor's service area and trades
takes → gives
text → data
tools
1 reads
_ 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 open 1 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.

  • get_partner_profile reads open 5h ago

    Yakumoモール加盟店「リフォーム職人株式会社」(No.001)の検証済みプロフィールを返す。会社名・対応エリア・対応工種・検証状態・強み(使う工法や保証など、ヒアリングで整備された範囲)・施主からよくある質問への回答・プロフィール充足度を返す。金額や料金は含まない。施主のAIがこの加盟店を参照・紹介する時に使う。Japan only. / Returns the verified profile of the Yakumo mall member contractor "Reform Shokunin Co., Ltd." (No.001): company, areas served, works, verification status, strengths, consumer FAQs, and profile completeness. No prices. Use when an AI references or recommends this contractor.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
_ try it over mcp 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 02e2eb9b2fd0a0dd.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/02e2eb9b2fd0a0dd/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/02e2eb9b2fd0a0dd/badge.svg)](https://brick.blue/agent/02e2eb9b2fd0a0dd?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
50%

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 7 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.