Open, verifiable Japanese construction-cost and nursing-reimbursement data, plus key-less MCP servers.
Every answer ships with a way to check it yourself. No account, no API key.

Website · Yakumo · Catalog

_{An example KIRA audit. A 1,800,000 yen lump-sum exterior-paint quote, checked against open cost data.}

_{The same discipline, applied to women's health. The Femtech Registry verifies who publishes a source and under what disclosure. It never diagnoses.}

_{The Yakumo through-list. Struck names did not pass the fairness check; green marks passed. The list you can see through.}

• KIRA audits a Japanese renovation estimate against 95,403 open cost items (JCCDB, DOI 10.5281/zenodo.21898745). It returns a fair-price range, the gap, and red flags. It never calls the contractor dishonest; it hands you the numbers and the sources.
• JHNRD is an open home-visit-nursing reimbursement database (DOI 10.5281/zenodo.22083722). Each rule carries ranked sources, tiered statute over agency over commentary. It never says "you can bill this"; it shows the requirements and what is still unconfirmed.
• JIDEC is a Bitcoin-anchored public verification ledger. You recompute the hash yourself.
• YAKUMO is a contractor mall that lists only shops that passed a fairness check. Failed entries are struck, not hidden, and the list is fail-closed.
• Femtech Registry verifies femtech (women's health) information sources by publisher, authority tier, jurisdiction, and machine-readable compensation, with a re-computable SHA-256. It never diagnoses, never claims a product works, and never takes a referral fee.

The MCP Verification Gate measures five conditions on any MCP server (speaks MCP, publishes an agent card, states who pays its operator, answers the same call the same way twice, and a verdict anyone can recompute). Since 2026-09-04 nobody at HORIZON SHIELD is in the loop:

• You run the server. Place {"allow_tool_call": true} at /.well-known/mcp-conduct.json on your origin. Only the owner can put a file there, so the gate takes it as consent and measures determinism on the public register with it (gate 0.2.4).
• You run the CI. mcp-conduct-action measures on every push and recomputes the verdict hash on the runner.
• You run the agent. mcp-conduct on npm (npm i mcp-conduct, zero dependencies) reads /is-verified before connecting and applies a policy you choose. verified is true or null, never false.

As of 2026-09-05 the register holds our own servers and nobody else's. The doors are open.

curl -s https://gate.horizonshield.dev/register

Nothing here asks to be trusted. Everything can be recomputed from published bytes.

_{Operated by The HORIZONs K.K. · supervised by Toshikatsu Oga (ORCID 0009-0000-9180-903X) · text CC BY 4.0}