mcpbeat

Design Engine MCP Server

io.aidc-ai/design-engine
not responding

Design Engine is listed as active in the registry but did not answer our last check. It exposes 3 tools.

AI data-center design engine: size, validate & lay out Rubin-era data centers. Korea live.

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
0.0%
Uptime 24h
0 of 91 checks
3
Tools
read from the server
79 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add design-engine --transport http https://aidc-ai.io/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "design-engine": {
      "url": "https://aidc-ai.io/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.design-engine]
url = "https://aidc-ai.io/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "design-engine": {
      "url": "https://aidc-ai.io/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "design-engine": {
      "url": "https://aidc-ai.io/api/mcp"
    }
  }
}

Available tools 3

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

design
design
Generate a profile-aware AI data center design basis from IT load, rack density, GPU generation, site area, region, and optional project inputs.
layout
layout
Generate profile-aware physical rack blocks, rack-plan candidates, and site layout data from a nested design request.
validate
validate
Validate a previous design summary or raw design input against electrical, cooling, layout, safety, and data rules. Private EngineSessions are not exposed through public MCP.

Endpoints

URLTransportStateLatencyChecked
https://aidc-ai.io/api/mcp streamable-http answering 79 ms 14 min ago

Design Engine — questions

Answers built from our own checks of this server.

What can Design Engine do?
It exposes 3 tools, read directly from the server on our last check. Among them: design, layout, validate. 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 Design Engine working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 79 ms. The bar chart above shows every period we have measured.
The registry lists Design Engine as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Design Engine?
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 Design Engine need an API key?
No. Design Engine completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.