mcpbeat Sign in

Device House MCP Server

answering

Device House is answering right now. Last checked 16 min ago. It exposes 21 tools.

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

Uptime history 52 days of history · worst day 99%
52 days agonow
98.9%
Uptime 24h
90 of 91 checks
21
Tools
read from the server
1141 ms
Response time
average over 24h
open, no key
Access
streamable-http

Device House missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 16 min ago.

run in your terminal
claude mcp add device-house --transport http https://device-house-mcp.fly.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "device-house": {
      "url": "https://device-house-mcp.fly.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.device-house]
url = "https://device-house-mcp.fly.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "device-house": {
      "url": "https://device-house-mcp.fly.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "device-house": {
      "url": "https://device-house-mcp.fly.dev/mcp"
    }
  }
}

Available tools 21

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

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

Endpoints

URLTransportStateLatencyChecked
https://device-house-mcp.fly.dev/mcp streamable-http answering 407 ms 16 min ago

Alternatives to Device House

same job, measured the same way
Source Parts
by sourceparts

Electronic component sourcing, BOM management, and PCB design workflows.

207 installs/wk answering
Bimhouse
by bim

bim.house — words become buildings. Generate BIM, check code & structure, quote materials.

29 tools answering
Refero
by referodesign

Search curated design styles, real product screens, and user flows for evidence-based design work.

answering
Firmware Test Farm MCP
by oxyvore-cyber

Flash and run real firmware on physical embedded dev boards from an AI agent, over MCP.

answering
FormulaSignal
by formulasignal

Dated formula history, confirmed changes and evidence for U.S. pre-workout supplements.

18 tools answering
Who Do I Call For? — Emergency Home-Service Router
by woodydaniel

Routes home emergencies to the right trade: who to call in what order, first steps, sourced costs.

3 tools answering
Hex Image Audit
by jmshinhwa

Recomputes every record checksum in a .hex or .s19 firmware image and names the bad records, the ove

575 installs/wk local only
Wortwert
by thomas0369

Gematria and pattern decoder for words, sacred texts, news, dates, and Human Design.

answering

Device House — questions

Answers built from our own checks of this server.

What can Device House do?
It exposes 21 tools, read directly from the server on our last check. Among them: autoroute, compliance_check, eval_device, fab_order_package, generate_device, get_bom_csv and 15 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Device House working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 1141 ms. The bar chart above shows every period we have measured.
How do I connect Device House?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Device House need an API key?
No. Device House completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 21 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Device House?
It answers our handshake in 1141 ms on average, which is faster than 8% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.