Yakumo verified contractor No.001: Reform Shokunin Co., Ltd. (Aichi, Japan)
REMOTE · P001.HORIZONSHIELD.DEV
Verified profile of Reform Shokunin Co., Ltd., a Yakumo member renovation contractor in Aichi.
Available components
Last scanned (10 hours ago)
Scores higher than 70% of remote servers
Reachable. Last reached 24 Oct 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 Security54
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 183 tokens (~183/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 40. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 30. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
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://p001.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 p001.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 |
| p001.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://p001.horizonshield.dev/mcp | Verified | 200 | |
| http (plaintext) | http://p001.horizonshield.dev/mcp | Served over HTTP | 200 |
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 →
get_partner_profile 加盟店プロフィール取得 ~183
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string|null | – | – |
| found | boolean | yes | true only when a stored record was returned. |
| hearing_lookup | string | – | The secondary read (hearing data, which fills in strengths). If this is 'failed' the profile is returned but is incomplete, and says so here rather than looking thin. |
| lookup | string | yes | ok = the record was read and exists. absent = the read SUCCEEDED and there is no record yet. A read that FAILED never appears here: it is returned as a tool error (isError: true) with no profile, so… |
| note | string | – | – |
| store_id | string | – | – |
| verification | string | – | – |
No examples provided.
How do I install the Yakumo verified contractor No.001: Reform Shokunin Co… MCP server?
Yakumo verified contractor No.001: Reform Shokunin Co… is a hosted endpoint at https://p001.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 · p001.horizonshield.dev
claude mcp add --transport http ogasurfproject-jpg-hs-partner-001-mcp 'https://p001.horizonshield.dev/mcp'
What is the Yakumo verified contractor No.001: Reform Shokunin Co… MCP server?
Yakumo verified contractor No.001: Reform Shokunin Co… is an MCP server listed in the public MCP registry as io.github.ogasurfproject-jpg/hs-partner-001-mcp. Verified profile of Reform Shokunin Co., Ltd., a Yakumo member renovation contractor in Aichi. This page covers its hosted endpoint (https://p001.horizonshield.dev/mcp).
Is the Yakumo verified contractor No.001: Reform Shokunin Co… MCP server safe to use?
Yakumo verified contractor No.001: Reform Shokunin Co… scores 76 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 Yakumo verified contractor No.001: Reform Shokunin Co… MCP server expose?
Yakumo verified contractor No.001: Reform Shokunin Co… exposes 1 tool: get_partner_profile. Their descriptions and schemas cost roughly 183 tokens of context every time the server is loaded.
Does the Yakumo verified contractor No.001: Reform Shokunin Co… MCP server require authentication?
No. We connected to Yakumo verified contractor No.001: Reform Shokunin Co… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Yakumo verified contractor No.001: Reform Shokunin Co… MCP server still maintained?
Yakumo verified contractor No.001: Reform Shokunin Co… 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.