Agent Tools
List
Back to MCP servers

house.device/device-house

https://device-house-mcp.fly.dev/mcp
● healthy

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

What we measured

Over the last 30 days we probed this MCP server 30 times on 30 days; it answered 30 (100%). Median response 321 ms, 95th percentile 3,952 ms.

When we called tools/list it returned 21 tools, including list_archetypes, list_catalog, generate_device, over MCP protocol revision 2025-11-25.

Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 75% and higher on readiness than 55%.

From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure

Tools (21)

As returned by the server's own tools/list when we called it.

list_archetypes
device.houseが言葉から設計できるデバイス種別の一覧
list_catalog
選べるデバイス・カタログ(bim.house等が家の部屋に置く用)。価格/寸法/推奨部屋/ディープリンク付き
generate_device
言葉(用途)からデバイスを設計し、BoM/筐体/価格/全軸スコアを返す
eval_device
言葉から設計したデバイスの生成品質を5軸(意図/部品/作れる/完成/正直)で採点
compliance_check
言葉から設計したデバイスの規制適合(技適/PSE/CE/FCC/RoHS+発注先+部品調達)を機械チェック。設計で制御可能な指標は判定、実世界の試験/申請は要対応で正直表示(盛らない)
get_firmware
言葉から設計したデバイスのArduinoファーム雛形(.ino)を返す
get_netlist
配線ネットリスト(autorouteの入力)を返す
get_placement
JLCPCB部品配置(CPL CSV)を返す
autoroute
2層オートルータで実配線し、配線率/ビア数のサマリを返す(盛らない=未配線はfailed)
get_pcb_svg
配線済みPCBの2層プレビュー(SVG・赤=表/青=裏/金=パッド/点線=未配線)を返す
fab_order_package
発注パッケージ概要(配線済みGerber+BOM+CPL+手順一式)。JLCPCBにアップロード→支払いで発注。盛らない=実支払いは人間ゲート
manufacturing_readiness
製造レディネス(正直な実体評価): 実フットプリント/LCSC/DRC/fits/配線。発注して動く基板にできるか
get_kicad_netlist
KiCadネットリスト(.net)を出力。KiCadに取り込んで検証済みフットプリント割当・配線・DRC=量産正規ルート
get_bom_csv
JLCPCB形式のBOM CSV(Comment,Designator,Footprint,LCSC)を返す。LCSC番号は未検証のため空欄
parts_stats
パーツ・カタログの概観(総数/分類別)
parts_list
パーツ一覧(分類/インターフェイスでフィルタ可)
parts_search
パーツをキーワード検索(型番/説明/用途)
parts_get
id でパーツ1件取得
parts_add
パーツを追加(ユーザーカタログに永続)。idは省略可(型番からslug生成)
parts_update
既存パーツを更新(組み込み部品の価格/調達先などの上書きも可)
parts_remove
パーツを削除(組み込みはtombstoneで非表示化・再追加で復活)
Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

B · 82/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here C+, 66.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 24/25 Endpoint answers the MCP initialize handshake (3692 ms); slow response -1.
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 30/30 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 21 tool(s) with descriptions.
Verified identity 7/10 Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags 0/5 not seen in a source for over 30 days.
Auth declaration 0/5 How to authenticate is not stated.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Slow (3692 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-12.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.

Readiness
Higher than 55% of peers
This listing 82 · peer median 81
Latency
Faster than 75% of peers
This listing 176 ms · peer median 349 ms

Where it loses the most points, and how to win them back

  • Freshness + modern flags −5 — Keep the listing current in the registry or source it comes from.
    Now: not seen in a source for over 30 days.
  • Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
    Now: How to authenticate is not stated.
  • Verified identity −3 — Claim the listing and prove control of its domain.
    Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

mcp-registry since 2026-06-12 ↗ wellknown since 2026-09-23 ↗ agenstry since 2026-10-22 ↗ capkey since 2026-10-26 ↗

How to connect

MCP endpoint (streamable-http)
https://device-house-mcp.fly.dev/mcp
JSON-RPC initialize probe
curl -X POST https://device-house-mcp.fly.dev/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://device.house