Home / MCP registry index / io.github.ogasurfproject-jpg/construction-cost-data
HORIZON SHIELD Construction Cost Data: JCCDB (Japan) and USCCDB (United States)
io.github.ogasurfproject-jpg/construction-cost-data in the official MCP registry.
Endpoint https://ccdb.horizonshield.dev/mcp. Source: github.com/ogasurfproject-jpg/horizon-shield.
The registry describes it as: Public construction cost data for Japan and the U.S., each row with its source URL and licence.
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
search_jccdb_items get_jccdb_observations get_jccdb_labor_rate compare_jccdb_regions get_jccdb_work_unit_price get_jccdb_index_series get_us_construction_prices get_jccdb_coverage get_us_prevailing_wage get_us_permits get_us_area_factor get_us_price_chain get_us_import_landed_cost get_us_trade_margins get_us_contract_discounts
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-construction-cost-data)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.