house.device/device-house
REMOTE · DEVICE-HOUSE-MCP.FLY.DEV · SCANNED SEP 26
device.house — words become circuits. Design devices: BoM, enclosure, firmware, routed PCB.
Available components
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 Security57
- 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 21 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1100 tokens (~52/item across 21 items; 21 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage68
- 95% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 13% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "eval_device" implies "eval" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the house.device/device-house MCP server?
house.device/device-house is a hosted endpoint at https://device-house-mcp.fly.dev/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 · device-house-mcp.fly.dev
claude mcp add --transport http house-device-device-house 'https://device-house-mcp.fly.dev/mcp'
{
"mcpServers": {
"house-device-device-house": {
"url": "https://device-house-mcp.fly.dev/mcp"
}
}
} {
"servers": {
"house-device-device-house": {
"type": "http",
"url": "https://device-house-mcp.fly.dev/mcp"
}
}
} [mcp_servers.house-device-device-house] url = "https://device-house-mcp.fly.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"house-device-device-house": {
"type": "remote",
"url": "https://device-house-mcp.fly.dev/mcp",
"enabled": true
}
}
} openclaw mcp add house-device-device-house --url 'https://device-house-mcp.fly.dev/mcp' --transport streamable-http
mcp_servers:
house-device-device-house:
url: "https://device-house-mcp.fly.dev/mcp" {
"McpServers": {
"house-device-device-house": {
"Transport": "http",
"Url": "https://device-house-mcp.fly.dev/mcp"
}
}
} assistant mcp add house-device-device-house -t streamable-http -u 'https://device-house-mcp.fly.dev/mcp'
{
"mcpServers": {
"house-device-device-house": {
"type": "http",
"url": "https://device-house-mcp.fly.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 26 Sept 2026 · Probed https://device-house-mcp.fly.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fly.dev | CN=YE1,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 688c4daf5300c51e0a5c1f6837a3a67a868 |
| SANs: *.fly.dev | ||||||
| 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 device-house-mcp.fly.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fly.dev. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://device-house-mcp.fly.dev/mcp | Verified | 200 | |
| http (plaintext) | http://device-house-mcp.fly.dev/mcp | HTTPS enforced | 301 | https://device-house-mcp.fly.dev/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 →
autoroute ~54
2層オートルータで実配線し、配線率/ビア数のサマリを返す(盛らない=未配線はfailed)
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | – |
No output schema declared.
No examples provided.
compliance_check ~101
言葉から設計したデバイスの規制適合(技適/PSE/CE/FCC/RoHS+発注先+部品調達)を機械チェック。設計で制御可能な指標は判定、実世界の試験/申請は要対応で正直表示(盛らない)
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | 評価したいデバイスを言葉で |
No output schema declared.
No examples provided.
eval_device ~51
言葉から設計したデバイスの生成品質を5軸(意図/部品/作れる/完成/正直)で採点
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | – |
No output schema declared.
No examples provided.
fab_order_package ~73
発注パッケージ概要(配線済みGerber+BOM+CPL+手順一式)。JLCPCBにアップロード→支払いで発注。盛らない=実支払いは人間ゲート
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | – |
| qty | number | – | – |
No output schema declared.
No examples provided.
generate_device ~77
言葉(用途)からデバイスを設計し、BoM/筐体/価格/全軸スコアを返す
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | 作りたいデバイスを言葉で。例: 焚き火に声で参加できる音声デバイス |
No output schema declared.
No examples provided.
get_bom_csv ~52
JLCPCB形式のBOM CSV(Comment,Designator,Footprint,LCSC)を返す。LCSC番号は未検証のため空欄
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | – |
No output schema declared.
No examples provided.
get_firmware ~40
言葉から設計したデバイスのArduinoファーム雛形(.ino)を返す
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | – |
No output schema declared.
No examples provided.
get_kicad_netlist ~62
KiCadネットリスト(.net)を出力。KiCadに取り込んで検証済みフットプリント割当・配線・DRC=量産正規ルート
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | – |
No output schema declared.
No examples provided.
get_netlist ~31
配線ネットリスト(autorouteの入力)を返す
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | – |
No output schema declared.
No examples provided.
get_pcb_svg ~55
配線済みPCBの2層プレビュー(SVG・赤=表/青=裏/金=パッド/点線=未配線)を返す
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | – |
No output schema declared.
No examples provided.
get_placement ~30
JLCPCB部品配置(CPL CSV)を返す
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | – |
No output schema declared.
No examples provided.
list_archetypes ~28
device.houseが言葉から設計できるデバイス種別の一覧
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_catalog ~77
選べるデバイス・カタログ(bim.house等が家の部屋に置く用)。価格/寸法/推奨部屋/ディープリンク付き
| Name | Type | Req | Description |
|---|---|---|---|
| room | string | – | 推奨部屋でフィルタ: entrance/living/bedroom/kitchen/outdoor等 |
No output schema declared.
No examples provided.
manufacturing_readiness ~60
製造レディネス(正直な実体評価): 実フットプリント/LCSC/DRC/fits/配線。発注して動く基板にできるか
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | – |
No output schema declared.
No examples provided.
parts_add ~105
パーツを追加(ユーザーカタログに永続)。idは省略可(型番からslug生成)
| Name | Type | Req | Description |
|---|---|---|---|
| cat | string | – | – |
| desc | string | – | – |
| footprint | array | – | – |
| id | string | – | – |
| interface | string | – | – |
| keywords | array | – | – |
| part | string | yes | 型番 例: BME680 |
| src | string | – | – |
| unit | number | – | – |
No output schema declared.
No examples provided.
parts_get ~24
id でパーツ1件取得
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
parts_list ~39
パーツ一覧(分類/インターフェイスでフィルタ可)
| Name | Type | Req | Description |
|---|---|---|---|
| cat | string | – | – |
| interface | string | – | – |
No output schema declared.
No examples provided.
parts_remove ~39
パーツを削除(組み込みはtombstoneで非表示化・再追加で復活)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
parts_search ~29
パーツをキーワード検索(型番/説明/用途)
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
parts_stats ~24
パーツ・カタログの概観(総数/分類別)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
parts_update ~49
既存パーツを更新(組み込み部品の価格/調達先などの上書きも可)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| patch | object | yes | – |
No output schema declared.
No examples provided.
What is the house.device/device-house MCP server?
house.device/device-house is an MCP server listed in the public MCP registry as house.device/device-house. device.house, words become circuits. Design devices: BoM, enclosure, firmware, routed PCB. This page covers its hosted endpoint (https://device-house-mcp.fly.dev/mcp).
Is the house.device/device-house MCP server safe to use?
house.device/device-house scores 74 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.device/device-house MCP server expose?
house.device/device-house exposes 21 tools: list_archetypes, list_catalog, generate_device, eval_device, compliance_check, and 16 more. Their descriptions and schemas cost roughly 1,100 tokens of context every time the server is loaded.
Does the house.device/device-house MCP server require authentication?
No. We connected to house.device/device-house without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the house.device/device-house MCP server still maintained?
house.device/device-house is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.