MCP QUEEN
house.device/device-house B
device.house — words become circuits. Design devices: BoM, enclosure, firmware, routed PCB.
Media & Designv1.0.0streamable-httpdevice-house-mcp.fly.dev
Grade evidence — probed 2026-07-13 11:45 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 307ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo device-house@0.1.0 |
| tooling | 30 / 35 | tools/list OK: 21 tools e.g. "list_archetypes"; 21/21 described, 21/21 fully-typed schemas, median description 35 chars |
| latency | 10 / 10 | initialize round-trip 307ms |
| provenance | 5 / 15 | description present; no repository URL; version 1.0.0; namespace house.device does NOT match remote host (expected *.device.house) |
Score 85/100 · latency 307ms · 21 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http device-house https://device-house-mcp.fly.dev/mcp
Generic MCP client config:
{ "mcpServers": { "device-house": { "type": "http", "url": "https://device-house-mcp.fly.dev/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/house.device/device-house · referral link https://mcpqueen.com/go/house.device/device-house (counts as “routed via the queen”).
Own this server? Embed your grade badge
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/house.device/device-house)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 11:45 | B | 85 | 307ms |