house.device/device-house

REMOTE · DEVICE-HOUSE-MCP.FLY.DEV · SCANNED AUG 3

device.house — words become circuits. Design devices: BoM, enclosure, firmware, routed PCB.

Available components

+6 this week 57 57 Trust /100

Trust breakdown (6 categories)

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 →

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 Usability43

AI-judged instruction clarity (poor).Fail
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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · device-house-mcp.fly.dev

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http house-device-device-house https://device-house-mcp.fly.dev/mcp

# ~/.codex/config.toml

[mcp_servers.house-device-device-house]
url = "https://device-house-mcp.fly.dev/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "house-device-device-house": {
      "type": "remote",
      "url": "https://device-house-mcp.fly.dev/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add house-device-device-house --url https://device-house-mcp.fly.dev/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  house-device-device-house:
    url: "https://device-house-mcp.fly.dev/mcp"

// mcp.json

{
  "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.

Changelog

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.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 +1
- 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 50

First indexed and scored.

Show 5 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 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=YE2,O=Let's Encrypt,C=US	21 Jun 2026	19 Sept 2026	ECDSA 256	ECDSA-SHA384	503153e73302e4a0c89ebb83c4a741aac04
SANs: *.fly.dev
CN=YE2,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	4df3b15dd6c0784c507cd37b58e6f115
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

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

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

MCP tools — 21 exposed · ~1,100 tokens

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.

Tool Tokens

autoroute ~54

2層オートルータで実配線し、配線率/ビア数のサマリを返す(盛らない=未配線はfailed)

Input Output Examples

Name	Type	Req	Description
prompt	string	yes	—

No output schema declared.

No examples provided.

compliance_check ~101

言葉から設計したデバイスの規制適合(技適/PSE/CE/FCC/RoHS+発注先+部品調達)を機械チェック。設計で制御可能な指標は判定、実世界の試験/申請は要対応で正直表示(盛らない)

Input Output Examples

Name	Type	Req	Description
prompt	string	yes	評価したいデバイスを言葉で

No output schema declared.

No examples provided.

eval_device ~51

言葉から設計したデバイスの生成品質を5軸(意図/部品/作れる/完成/正直)で採点

Input Output Examples

Name	Type	Req	Description
prompt	string	yes	—

No output schema declared.

No examples provided.

fab_order_package ~73

発注パッケージ概要(配線済みGerber+BOM+CPL+手順一式)。JLCPCBにアップロード→支払いで発注。盛らない=実支払いは人間ゲート

Input Output Examples

Name	Type	Req	Description
prompt	string	yes	—
qty	number	—	—

No output schema declared.

No examples provided.

generate_device ~77

言葉(用途)からデバイスを設計し、BoM/筐体/価格/全軸スコアを返す

Input Output Examples

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番号は未検証のため空欄

Input Output Examples

Name	Type	Req	Description
prompt	string	yes	—

No output schema declared.

No examples provided.

get_firmware ~40

言葉から設計したデバイスのArduinoファーム雛形(.ino)を返す

Input Output Examples

Name	Type	Req	Description
prompt	string	yes	—

No output schema declared.

No examples provided.

get_kicad_netlist ~62

KiCadネットリスト(.net)を出力。KiCadに取り込んで検証済みフットプリント割当・配線・DRC=量産正規ルート

Input Output Examples

Name	Type	Req	Description
prompt	string	yes	—

No output schema declared.

No examples provided.

get_netlist ~31

配線ネットリスト(autorouteの入力)を返す

Input Output Examples

Name	Type	Req	Description
prompt	string	yes	—

No output schema declared.

No examples provided.

get_pcb_svg ~55

配線済みPCBの2層プレビュー(SVG・赤=表/青=裏/金=パッド/点線=未配線)を返す

Input Output Examples

Name	Type	Req	Description
prompt	string	yes	—

No output schema declared.

No examples provided.

get_placement ~30

JLCPCB部品配置(CPL CSV)を返す

Input Output Examples

Name	Type	Req	Description
prompt	string	yes	—

No output schema declared.

No examples provided.

list_archetypes ~28

device.houseが言葉から設計できるデバイス種別の一覧

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_catalog ~77

選べるデバイス・カタログ(bim.house等が家の部屋に置く用)。価格/寸法/推奨部屋/ディープリンク付き

Input Output Examples

Name	Type	Req	Description
room	string	—	推奨部屋でフィルタ: entrance/living/bedroom/kitchen/outdoor等

No output schema declared.

No examples provided.

manufacturing_readiness ~60

製造レディネス(正直な実体評価): 実フットプリント/LCSC/DRC/fits/配線。発注して動く基板にできるか

Input Output Examples

Name	Type	Req	Description
prompt	string	yes	—

No output schema declared.

No examples provided.

parts_add ~105

パーツを追加(ユーザーカタログに永続)。idは省略可(型番からslug生成)

Input Output Examples

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件取得

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

parts_list ~39

パーツ一覧(分類/インターフェイスでフィルタ可)

Input Output Examples

Name	Type	Req	Description
cat	string	—	—
interface	string	—	—

No output schema declared.

No examples provided.

parts_remove ~39

パーツを削除(組み込みはtombstoneで非表示化・再追加で復活)

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

parts_search ~29

パーツをキーワード検索(型番/説明/用途)

Input Output Examples

Name	Type	Req	Description
query	string	yes	—

No output schema declared.

No examples provided.

parts_stats ~24

パーツ・カタログの概観(総数/分類別)

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

parts_update ~49

既存パーツを更新(組み込み部品の価格/調達先などの上書きも可)

Input Output Examples

Name	Type	Req	Description
id	string	yes	—
patch	object	yes	—

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	50
27 Jul	51
28 Jul	52
29 Jul	52
30 Jul	53
31 Jul	56
1 Aug	56
2 Aug	57
3 Aug	57