mcp-registry/house.bim/bimhouse · v1.0.0
As of 2026-10-26 21:20 UTC, the Bim Bimhouse MCP server is up with a Glimind reliability score of 78/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 50 outages in 90 days, with a median recovery of 3 minutes.
bim.house — words become buildings. Generate BIM, check code & structure, quote materials.
Point your MCP client at this streamable-http endpoint: https://bim.house/mcp
29 of 29 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
11 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
14 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fhouse.bim%2Fbimhouse/fixes
{
"name": "admin_set_site_context",
"description": "[EN] Bulk-set site conditions for any houses (admin only, admin_token; no edit_token). Pass `entries`: [{slug, zoning?, road_width_m?, high_district?, fire_district?, climate_zone?, latitude?, neighbor_setback_m?, min_lot_area_m2?, shadow_regulation?}]. DB + cache applied immediately. For operators to backfill zoning/road-width (e.g. from reinfolib) across all properties. / 任意の物件の敷地条件を一括上書き (管理者のみ・edit_token 不要)。entries 配列で複数物件をまとめて投入。DB+キャッシュ即時反映。用途地域/道路幅員等の実データを全物件へ流し込む運用者向け。",
"inputSchema": {
"type": "object",
"required": [
"admin_token"
],
"properties": {
"slug": {
"type": "string",
"description": "単一指定する場合 (entries の代わり)"
},
"entries": {
"type": "array",
"items": {
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string"
}
}
},
"description": "物件ごとの敷地条件。各要素は {slug(必須), zoning?, road_width_m?, north_setback_m?, neighbor_setback_m?, high_district?, fire_district?, climate_zone?, latitude?, min_lot_area_m2?, shadow_regulation?}"
},
"admin_token": {
"type": "string",
"description": "管理者トークン (必須)"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": true
}
}{
"name": "create_house",
"description": "[EN] Build a new house (bim.json) from an address alone (geocoded, auto-named, climate-aware) or full elements; returns slug + edit_token + viewer/permit URLs + inline houki & structure verdicts. No auth (private by default, rate-limited). / 新しい物件 (bim.json) を作成する。name か address のどちらか必須 — 住所だけ渡せば geocode で座標を引き「<地名>の家」と自動命名して家が建つ (REINFOLIB_KEY 設定時は用途地域も実値注入)。elements (bim.json v1 要素配列) を渡すとそのまま保存、省略すると敷地寸法から住宅 BIM を自動生成。name/rooms に「薪ストーブ・土間・ロフト・カーポート・書斎・ピアノ・サウナ」等の言葉が入ると対応する要素 (煙突・炉台・はしご込み) を自動",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"name": {
"type": "string",
"description": "物件名 (address を渡せば省略可 — 地名から自動命名)"
},
"rooms": {
"type": "string",
"description": "室構成サマリー"
},
"floors": {
"type": "integer",
"description": "階数 (既定 1)"
},
"zoning": {
"type": "string",
"description": "用途地域 (例: 近隣商業地域)"
},
"address": {
"type": "string",
"description": "所在地 (これだけでも家が建つ。geocode で座標解決・気候/積雪も住所から自動設定)"
},
"lot_d_m": {
"type": "number",
"description": "奥行 m (簡易シェル生成に使用)"
},
"lot_w_m": {
"type": "number",
"description": "間口 m (簡易シェル生成に使用)"
},
"private": {
"type": "boolean",
"description": "true で物件一覧 (/property) に非掲載・直リンクのみ。既定 false=掲載。"
},
"elements": {
"type": "array",
"items": {
"type": "object"
},
"description": "bim.json v1 要素配列。各要素 {id,cls,label,descr,shape:'box'|'cylinder',x,y,z,w,d,h,rotation?} (mm)。省略可。"
},
"gross_m2": {
"type": "number",
"description": "延床面積 ㎡"
},
"structure": {
"type": "string",
"description": "構造 (例: RC 打放しコンクリート)"
},
"land_area_m2": {
"type": "number",
"description": "敷地面積 ㎡"
},
"project_type": {
"enum": [
"new",
"renovation",
"change_of_use"
],
"type": "string",
"description": "[EN] 'new' (default) builds a from-scratch cost estimate. 'renovation'/'change_of_use' treat this as an EXISTING building being remodeled: foundation/frame/roof default to ¥0 (reused as-is) and only the trades in renovation_scope are costed at renovation unit rates. / 既定は new=新築(ゼロから建てる前提の概算)。renovation/change_of_use を指定すると『既存建物の改修』として扱われ、基礎・躯体・屋根等は既定でコスト¥0(既存流用)になり、renovation_scope で指定した工種だけを改修単価で見積もる。get_build_plan の結果も新築フル工程でなく改修工程 (解体・調査系を含む) に切り替わる。"
},
"construction_jpy": {
"type": "integer",
"description": "概算工事費 円"
},
"renovation_scope": {
"type": "array",
"items": {
"type": "string"
},
"description": "改修対象の工種 code 配列 (demo/interior/fittings/electrical/plumbing/hvac/roof/exterior/frame/found/temp/pv)。project_type=renovation|change_of_use のときのみ有効。省略時は典型的なフルリノベ (demo+内装+建具+電気+給排水+空調) を既定スコープとして使う。"
},
"seismic_retrofit": {
"type": "boolean",
"description": "true で耐震補強費 (建物全体延床×単価) を概算に含める。project_type=renovation|change_of_use のときのみ使う。"
},
"existing_year_built": {
"type": "integer",
"description": "既存建物の建築年 (西暦)。1981年5月以前は旧耐震 (耐震診断推奨)、2006年以前(または未指定)はアスベスト事前調査を概算に自動計上する。project_type=renovation|change_of_use のときのみ使う。"
},
"renovation_scope_m2": {
"type": "number",
"description": "実際に改修する範囲の面積㎡ (例: 3階建282㎡の建物のうち1階94㎡だけ改修するなら94)。省略時は gross_m2 (建物全体) を使う。project_type=renovation|change_of_use のときのみ有効。"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "create_product",
"description": "[EN] Register a new catalog product SKU (needs Bearer API key; insert-only, no overwrite). / 建材カタログ (products) に新しい製品 SKU を登録する。サッシ/窓/断熱材/照明/設備/家具/ドア等。Authorization: Bearer <APIキー> (/console で発行) が必須。登録後は /catalog と search_catalog に即反映。既存 SKU の上書きは不可 (insert-only)。",
"inputSchema": {
"type": "object",
"required": [
"sku",
"name",
"category"
],
"properties": {
"sku": {
"type": "string",
"description": "一意な SKU (英数・- _ . 、64字以内)。例: YKK-APW330-W"
},
"url": {
"type": "string",
"description": "メーカー公式ページ URL"
},
"name": {
"type": "string",
"description": "製品名 (必須)"
},
"spec": {
"type": "object",
"description": "追加スペック (任意の key/value オブジェクト)"
},
"tags": {
"type": "string",
"description": "カンマ区切りタグ"
},
"brand": {
"type": "string",
"description": "ブランド (例: YKK AP, LIXIL)"
},
"u_value": {
"type": "number",
"description": "熱貫流率 U値 W/m²K"
},
"category": {
"type": "string",
"description": "カテゴリ (必須)。例: サッシ, 窓, 断熱材, 照明, 設備, 家具, ドア"
},
"jan_code": {
"type": "string",
"description": "JAN コード"
},
"mfr_code": {
"type": "string",
"description": "メーカー型番"
},
"eta_value": {
"type": "number",
"description": "日射熱取得率 η値"
},
"ifc_class": {
"type": "string",
"description": "IFC クラス (省略時はカテゴリから推定。例: IFCWINDOW)"
},
"price_jpy": {
"type": "integer",
"description": "メーカー希望小売 税抜 円"
},
"description": {
"type": "string",
"description": "製品説明"
},
"install_jpy": {
"type": "integer",
"description": "施工費の目安 円"
},
"stock_status": {
"type": "string",
"description": "在庫 (in_stock/low_stock/order/made_to_order/discontinued。既定 in_stock)"
},
"lead_time_days": {
"type": "integer",
"description": "納期 (日)"
},
"warranty_years": {
"type": "integer",
"description": "保証年数"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/house.bim/bimhouse"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/house.bim/bimhouse"}) over MCP.
create_house ~796 tokenscreate_product ~433 tokensupdate_house ~372 tokensset_site_context ~369 tokensupsert_zoning_rule ~329 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fhouse.bim%2Fbimhouse?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fhouse.bim%2Fbimhouse?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fhouse.bim%2Fbimhouse.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fhouse.bim%2Fbimhouse.svg :target: https://glimind.com/server/mcp-registry%2Fhouse.bim%2Fbimhouse?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b01f3bbfbd753bde…, first seen 2026-10-17, included at leaf 8464 of 75,514. Version history · verify what your client received.
Compare: most reliable database servers · most reliable communication servers · most reliable productivity servers · most reliable data servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 21:20 UTC, the Bim Bimhouse MCP server is up with a Glimind reliability score of 78/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 50 outages in 90 days, with a median recovery of 3 minutes.
Bim Bimhouse MCP server advertises 29 tools, including admin_set_site_context, chat, create_house, create_product, delete_zoning_rule.
Point your MCP client at this streamable-http endpoint: https://bim.house/mcp
Glimind scanned all 29 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.