house.bim/bimhouse
REMOTE · BIM.HOUSE
bim.house — words become buildings. Generate BIM, check code & structure, quote materials.
Available components
Last scanned (19 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Developer Tools
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 Security63
- 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 25 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 4078 tokens (~163/item across 25 items; 25 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management62
- Stability check failed: schema churn in the 30 days we've observed: 11 tool removals, 0 breaking changes, 0 auth/transport breaks, 7 additions. See how to fix → Fail
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 25 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 25 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 0
- Stability: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 25 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 18 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 13 Nov 26 +1
- Schema quality: 3309 → 4078 ▼ functional
- New tool “import_contractor” functional
- New tool “list_contractors” functional
- New tool “list_pending_contractors” functional
- New tool “match_contractors” functional
- New tool “register_contractor” functional
- New tool “review_contractor” functional
- 12 Nov 26 0
- Schema quality: 2928 → 3309 ▼ functional
- New tool “update_house” functional
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 45 to 48.
- 10 Nov 26 0
- Stability: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 18 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 9 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 8 Nov 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 48 to 45.
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 21 Nov 2026 · Probed https://bim.house/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bim.house | CN=YE1,O=Let's Encrypt,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 599c8167472eb8c0e31d2e9a0dfa7cb2da8 |
| SANs: *.bim.house, bim.house | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bim.house. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| house. | DS published | 130 | 8 | Verified |
| bim.house. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' blob: https://static.cloudflareinsights.com https://unpkg.com https://cdn.jsdelivr.net https://cdn.skypack.dev https://js.stripe.com https://enabler-analytics.fly.dev https://koe.live https://www.googletagmanager.com https://googleads.g.doubleclick.net https://www.googleadservices.com https://www.google-analytics.com; script-src-elem 'self' 'unsafe-inline' blob: https://static.cloudflareinsights.com https://unpkg.com https://cdn.jsdelivr.net https://cdn.skypack.dev https://js.stripe.com https://enabler-analytics.fly.dev https://koe.live https://www.googletagmanager.com https://googleads.g.doubleclick.net https://www.googleadservices.com https://www.google-analytics.com; worker-src 'self' blob: https://cdn.jsdelivr.net; media-src 'self' data: blob:; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdn.jsdelivr.net https://unpkg.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' https: data: blob:; connect |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), microphone=(self), geolocation=(self), payment=(self "https://js.stripe.com") |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bim.house/mcp | Verified | 200 | |
| http (plaintext) | http://bim.house/mcp | HTTPS enforced | 301 | https://bim.house/mcp |
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 →
build_on_land ~195
緯度経度 (と任意で用途地域・敷地面積・名前) を指定して、その土地に家を建てる (create_house に座標+法規を注入)。スカウト地・紹介・設計ロイヤリティの台帳にも記録される。/earth の「この土地に建てる」と同じ API。
| Name | Type | Req | Description |
|---|---|---|---|
| area_m2 | number | – | 敷地面積 ㎡ (既定 165) |
| lat | number | yes | 緯度 |
| lng | number | yes | 経度 |
| name | string | – | 物件名 (省略時は座標から自動命名) |
| template_id | integer | – | 設計テンプレ ID (設計市場のものを使う場合) |
| zoning | string | – | 用途地域コード (省略時 none) |
No output schema declared.
No examples provided.
chat ~153
bim.house / MU の AI チャット。メール認証して /console で発行した API キーで認証必須 (Authorization: Bearer <APIキー>)。無料 5 回、以降は Pro ¥980/月で月 500 回 (買切クレジット併用可)。建築・BIM・法規・SIPs・MU について日本語で答える。引数 message (必須) と history (任意, [{role, content}])。
| Name | Type | Req | Description |
|---|---|---|---|
| history | array | – | 直前までの会話履歴 (任意) |
| message | string | yes | ユーザーの質問・メッセージ |
No output schema declared.
No examples provided.
create_house ~562
新しい物件 (bim.json) を作成する。name か address のどちらか必須 — 住所だけ渡せば geocode で座標を引き「<地名>の家」と自動命名して家が建つ (REINFOLIB_KEY 設定時は用途地域も実値注入)。elements (bim.json v1 要素配列) を渡すとそのまま保存、省略すると敷地寸法から住宅 BIM を自動生成。name/rooms に「薪ストーブ・土間・ロフト・カーポート・書斎・ピアノ・サウナ」等の言葉が入ると対応する要素 (煙突・炉台・はしご込み) を自動配置し、寒冷地住所ならトリプルガラス+付加断熱+雪止めに外皮を格上げ。「平屋」「2階建て」も階数に反映。slug と edit_token、viewer/json/permit URL と適用 features・site (座標/用途地域ソース) を返す。
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | 所在地 (これだけでも家が建つ。geocode で座標解決・気候/積雪も住所から自動設定) |
| construction_jpy | integer | – | 概算工事費 円 |
| elements | array | – | bim.json v1 要素配列。各要素 {id,cls,label,descr,shape:'box'|'cylinder',x,y,z,w,d,h,rotation?} (mm)。省略可。 |
| floors | integer | – | 階数 (既定 1) |
| gross_m2 | number | – | 延床面積 ㎡ |
| land_area_m2 | number | – | 敷地面積 ㎡ |
| lot_d_m | number | – | 奥行 m (簡易シェル生成に使用) |
| lot_w_m | number | – | 間口 m (簡易シェル生成に使用) |
| name | string | – | 物件名 (address を渡せば省略可 — 地名から自動命名) |
| private | boolean | – | true で物件一覧 (/property) に非掲載・直リンクのみ。既定 false=掲載。 |
| rooms | string | – | 室構成サマリー |
| structure | string | – | 構造 (例: RC 打放しコンクリート) |
| zoning | string | – | 用途地域 (例: 近隣商業地域) |
No output schema declared.
No examples provided.
create_product ~433
建材カタログ (products) に新しい製品 SKU を登録する。サッシ/窓/断熱材/照明/設備/家具/ドア等。Authorization: Bearer <APIキー> (/console で発行) が必須。登録後は /catalog と search_catalog に即反映。既存 SKU の上書きは不可 (insert-only)。
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | ブランド (例: YKK AP, LIXIL) |
| category | string | yes | カテゴリ (必須)。例: サッシ, 窓, 断熱材, 照明, 設備, 家具, ドア |
| description | string | – | 製品説明 |
| eta_value | number | – | 日射熱取得率 η値 |
| ifc_class | string | – | IFC クラス (省略時はカテゴリから推定。例: IFCWINDOW) |
| install_jpy | integer | – | 施工費の目安 円 |
| jan_code | string | – | JAN コード |
| lead_time_days | integer | – | 納期 (日) |
| mfr_code | string | – | メーカー型番 |
| name | string | yes | 製品名 (必須) |
| price_jpy | integer | – | メーカー希望小売 税抜 円 |
| sku | string | yes | 一意な SKU (英数・- _ . 、64字以内)。例: YKK-APW330-W |
| spec | object | – | 追加スペック (任意の key/value オブジェクト) |
| stock_status | string | – | 在庫 (in_stock/low_stock/order/made_to_order/discontinued。既定 in_stock) |
| tags | string | – | カンマ区切りタグ |
| u_value | number | – | 熱貫流率 U値 W/m²K |
| url | string | – | メーカー公式ページ URL |
| warranty_years | integer | – | 保証年数 |
No output schema declared.
No examples provided.
get_house_bim ~80
slug を指定して物件の完全な bim.json v1 (project メタ + elements 配列) を取得。include_elements=false でメタのみ。
| Name | Type | Req | Description |
|---|---|---|---|
| include_elements | boolean | – | elements を含めるか (既定 true) |
| slug | string | yes | 物件 slug (list_houses 参照) |
No output schema declared.
No examples provided.
get_land_listing ~76
slug を指定して 1 件の売地の詳細 (価格・面積・用途地域・AI 設計提案・座標) を取得。座標が未解決の場合は lat/lng が null。
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | 売地 slug (list_land_listings 参照) |
No output schema declared.
No examples provided.
get_product ~54
SKU を指定して 1 製品の詳細 (価格・性能値 U値/η値・在庫・JAN・後継品) を取得。
| Name | Type | Req | Description |
|---|---|---|---|
| sku | string | yes | 製品 SKU |
No output schema declared.
No examples provided.
houki_check ~66
建築基準法チェック (建ぺい率・容積率・北側/道路斜線・採光・換気) を houki-engine で実行し合否を返す。
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | 物件 slug |
No output schema declared.
No examples provided.
import_contractor ~214
【管理者専用】正規に確認した実在業者を出典つきで登録する。ADMIN_EMAILS に含まれる API キーのみ。source_url (一次情報 URL) 必須。承認済みで即掲載。
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | 連絡先 |
| fulfillment | string | – | labor / kit / both |
| lat | number | – | – |
| lead_time_days | integer | – | – |
| license_no | string | – | 建設業許可番号 |
| lng | number | – | – |
| name | string | yes | 会社名・屋号 (必須) |
| prefectures | – | – | 対応都道府県の配列、または CSV |
| service_radius_km | number | – | – |
| source_url | string | yes | 出典の一次情報 URL (必須。国交省検索システム等) |
| trades | – | – | 対応工種 code の配列、または 'all' |
No output schema declared.
No examples provided.
list_contractors ~108
登録済みの建築業者・工務店の一覧を返す。pref (都道府県) と trade (工種 code) で絞り込める。source='sample' は画面確認用の架空データで実在企業ではない。
| Name | Type | Req | Description |
|---|---|---|---|
| pref | string | – | 都道府県 (例: 東京都) |
| trade | string | – | 工種 code (例: found, frame, roof, electrical) |
No output schema declared.
No examples provided.
list_houses ~128
運営 curated 公開物件 (有名建築・巨大ランドマーク・SOLUNA 等) の一覧。slug / 規模 / 要素数 / bim.json 充足率(%) を返す。ユーザー作成物件 (u-*) は既定では含まない (直リンクで個別取得は可)。include_user=true で公開ユーザー物件も含める。
| Name | Type | Req | Description |
|---|---|---|---|
| include_user | boolean | – | 公開 (private=false) のユーザー作成物件も含める (既定 false) |
No output schema declared.
No examples provided.
list_land_listings ~179
現在販売中の土地 (SUUMO 実値ベース) の一覧を返す。価格・面積・用途地域・SUUMO リンク・座標 (geocode 済みのもの) を含む。max_price_jpy / min_area_m2 / q (住所・タイトル部分一致) で絞り込める。/earth 地図のオレンジピンと同じデータ。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | 最大件数 (1-100, 既定 50) |
| max_price_jpy | integer | – | 土地価格の上限 (円) |
| min_area_m2 | number | – | 敷地面積の下限 (㎡) |
| q | string | – | 住所・タイトルの部分一致キーワード |
No output schema declared.
No examples provided.
list_mine ~43
自分 (API キーのアカウント) が登録した製品の一覧を返す。Authorization: Bearer <APIキー> 必須。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_pending_contractors ~37
【管理者専用】承認待ち業者の一覧。ADMIN_EMAILS に含まれる API キーのみ。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
match_contractors ~88
物件 slug を指定し、その土地・工種に合う業者候補を返す。trade 省略時は全工種で集約。各工種ごとに上位5社を返す。
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | 物件 slug |
| trade | string | – | 工種 code (省略時は全工種) |
No output schema declared.
No examples provided.
material_quote ~109
カタログ連携の概算見積もり。BIM 要素 takeoff × 建材カタログ実価格 (窓/ドア/設備) + 原単位 (躯体/仕上げ) で BOM・総額・㎡単価を算出し、各資材の納期 (lead_time_days) と在庫、クリティカルパス納期も返す。
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | 物件 slug |
No output schema declared.
No examples provided.
probe_land ~144
緯度経度を指定して、その土地の Site IQ (地形・日射・災害リスク・法規ヘッドルーム・気候の 5 軸スコア) を採点する。zoning (用途地域コード) を渡すと法規スコアが再計算される。/earth 地図クリックと同じ API。
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | 緯度 (-90〜90) |
| lng | number | yes | 経度 (-180〜180) |
| zoning | string | – | 用途地域コード (例: low1, res1, shop。省略時 none) |
No output schema declared.
No examples provided.
register_contractor ~230
建築業者・工務店を登録する (セルフサーブ供給側)。Authorization: Bearer <APIキー> 必須。登録後は match_contractors と /contractors に反映される。
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | 連絡先 |
| fulfillment | string | – | labor / kit / both |
| lat | number | – | 拠点の緯度 |
| lead_time_days | integer | – | 標準納期 (日) |
| license_no | string | – | 建設業許可番号 (任意。承認時に国交省検索で照合) |
| lng | number | – | 拠点の経度 |
| name | string | yes | 会社名・屋号 (必須) |
| prefectures | – | – | 対応都道府県の配列、または CSV |
| service_radius_km | number | – | 対応半径 km (0=都道府県のみ) |
| trades | – | – | 対応工種 code の配列、または 'all' |
No output schema declared.
No examples provided.
retire_product ~68
自分が登録した製品を取り下げる (生産終了化。ハード削除はしない)。Authorization: Bearer <APIキー> 必須。他者/公式 SKU は不可。
| Name | Type | Req | Description |
|---|---|---|---|
| sku | string | yes | 取り下げる SKU (必須) |
No output schema declared.
No examples provided.
review_contractor ~92
【管理者専用】承認待ち業者を承認/却下する。ADMIN_EMAILS に含まれる API キーのみ。action=approve|reject。
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | approve / reject (必須) |
| contractor_id | integer | yes | 対象の業者 ID (必須) |
| reason | string | – | 却下理由 (reject 時) |
No output schema declared.
No examples provided.
search_catalog ~141
bim.house の建材・設備カタログ (3,800+ SKU) を検索。窓/断熱/設備/家具などを brand・category・キーワードで絞り込む。
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | ブランド完全一致 (例: YKK AP, LIXIL) |
| category | string | – | カテゴリ完全一致 (例: 窓, 断熱材, 設備) |
| limit | integer | – | 最大件数 (1-50, 既定 20) |
| q | string | – | キーワード (商品名・型番・JAN・タグを部分一致) |
No output schema declared.
No examples provided.
set_visibility ~119
物件の掲載/非掲載を切り替える。edit_token (create_house の返り値) が必要。private=true で物件一覧から非掲載 (直リンクは残る)。進化ループの低スコア物件の淘汰などに使う。
| Name | Type | Req | Description |
|---|---|---|---|
| edit_token | string | yes | create_house が返した edit_token (必須) |
| private | boolean | yes | true=非掲載 / false=掲載 |
| slug | string | yes | 物件 slug (必須) |
No output schema declared.
No examples provided.
update_house ~381
既存物件の BIM を更新する (要素の追加・差し替え・メタ修正)。会話で作った物件を「ロフトも足して」「プールも」のように続けて編集する時に使う。slug は必須。edit_token は同じ会話セッションで create_house した物件なら自動補完される (ユーザーが会話で提示した場合のみ明示的に渡す。推測・捏造しない)。design_brief に追加・変更したい内容を自由文で渡すと、既存要素を保ったまま該当する特徴要素を追加する。elements を渡すと全要素を差し替える。
| Name | Type | Req | Description |
|---|---|---|---|
| construction_jpy | integer | – | – |
| design_brief | string | – | 追加・変更したい内容の自由文 (例: ロフトとプールを追加) |
| edit_token | string | – | 編集トークン。同一セッションで作成した物件は省略可 (自動補完) |
| elements | array | – | bim.json v1 要素配列 (渡すと全要素を差し替え)。省略時は design_brief で追加。 |
| floors | integer | – | 階数。既存と異なる値を渡すと外殻を建て直す (例: 2→3階)。 |
| gross_m2 | number | – | 延床面積。既存と大きく異なる値を渡すと外殻を建て直す。 |
| name | string | – | – |
| rooms | string | – | – |
| slug | string | yes | 更新する物件 slug (必須) |
No output schema declared.
No examples provided.
update_product ~214
自分が create_product で登録した製品のフィールドを更新する。Authorization: Bearer <APIキー> 必須。他者/公式 SKU は更新不可。指定したフィールドのみ上書き。
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | – |
| category | string | – | – |
| description | string | – | – |
| eta_value | number | – | – |
| install_jpy | integer | – | – |
| jan_code | string | – | – |
| lead_time_days | integer | – | – |
| mfr_code | string | – | – |
| name | string | – | – |
| price_jpy | integer | – | – |
| sku | string | yes | 更新対象の SKU (必須) |
| spec | object | – | 追加スペック (上書き) |
| stock_status | string | – | in_stock/low_stock/order/made_to_order/discontinued |
| tags | string | – | – |
| u_value | number | – | – |
| url | string | – | – |
| warranty_years | integer | – | – |
No output schema declared.
No examples provided.
whoami ~61
API キー認証の確認。Authorization: Bearer <APIキー> (/console で発行) を付けると認証済みアカウントの email を返す。Web/CLI どちらからでも使える。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the house.bim/bimhouse MCP server?
house.bim/bimhouse is a hosted endpoint at https://bim.house/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 · bim.house
claude mcp add --transport http house-bim-bimhouse 'https://bim.house/mcp'
What is the house.bim/bimhouse MCP server?
house.bim/bimhouse is an MCP server listed in the public MCP registry as house.bim/bimhouse. bim.house, words become buildings. Generate BIM, check code & structure, quote materials. This page covers its hosted endpoint (https://bim.house/mcp).
Is the house.bim/bimhouse MCP server safe to use?
house.bim/bimhouse scores 71 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 house.bim/bimhouse MCP server expose?
house.bim/bimhouse exposes 25 tools: whoami, chat, search_catalog, get_product, list_houses, and 20 more. Their descriptions and schemas cost roughly 3,975 tokens of context every time the server is loaded.
Does the house.bim/bimhouse MCP server require authentication?
No. We connected to house.bim/bimhouse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the house.bim/bimhouse MCP server still maintained?
house.bim/bimhouse is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the house.bim/bimhouse MCP server?
VerifyMCP ran 12 checks on house.bim/bimhouse, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about house.bim/bimhouse: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.