house.device/device-house
house.device/device-house · 1.0.0
device.house — words become circuits. Design devices: BoM, enclosure, firmware, routed PCB.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 30 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://device-house-mcp.fly.dev/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 21 tools.
- Protocol
- 2025-06-18
- Calls itself
- device-house 0.1.0
- Handshake time
- 442 ms
- HTTP status
- 200
The tools it lists (21, as of 2 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
list_archetypesdevice.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_placementJLCPCB部品配置(CPL CSV)を返す
autoroute2層オートルータで実配線し、配線率/ビア数のサマリを返す(盛らない=未配線はfailed)
get_pcb_svg配線済みPCBの2層プレビュー(SVG・赤=表/青=裏/金=パッド/点線=未配線)を返す
fab_order_package発注パッケージ概要(配線済みGerber+BOM+CPL+手順一式)。JLCPCBにアップロード→支払いで発注。盛らない=実支払いは人間ゲート
manufacturing_readiness
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
house.device/device-house, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 120 days ago. The registry entry · device.house