Home / MCP registry index / io.github.ogasurfproject-jpg/horizon-shield
HORIZON SHIELD: construction and renovation estimate auditor
io.github.ogasurfproject-jpg/horizon-shield in the official MCP registry.
Endpoint https://mcp.horizonshield.dev/. Source: github.com/ogasurfproject-jpg/horizon-shield.
The registry describes it as: Fair-price checks for Japanese renovation quotes, with sources and recomputable records.
We read its 15 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_jccdb_dataset_info list_cost_categories search_cost_category get_estimate_reading_guide get_fair_price_sources get_price_range audit_estimate preview_reverse_estimate check_red_flags verify_fair_price create_ap2_fairness_attestation get_anonymous_estimate_review_link get_agent_card verify_integrity_claim find_verified_contractor
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-ogasurfproject-jpg-horizon-shield)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.