io.aidc-ai/design-engine
REMOTE · AIDC-AI.IO · SCANNED OCT 4
AI data-center design engine: size, validate & lay out Rubin-era data centers. Korea live.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the io.aidc-ai/design-engine MCP server?
io.aidc-ai/design-engine is a hosted endpoint at https://aidc-ai.io/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · aidc-ai.io
claude mcp add --transport http io-aidc-ai-design-engine 'https://aidc-ai.io/api/mcp'
{
"mcpServers": {
"io-aidc-ai-design-engine": {
"url": "https://aidc-ai.io/api/mcp"
}
}
} {
"servers": {
"io-aidc-ai-design-engine": {
"type": "http",
"url": "https://aidc-ai.io/api/mcp"
}
}
} [mcp_servers.io-aidc-ai-design-engine] url = "https://aidc-ai.io/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-aidc-ai-design-engine": {
"type": "remote",
"url": "https://aidc-ai.io/api/mcp",
"enabled": true
}
}
} openclaw mcp add io-aidc-ai-design-engine --url 'https://aidc-ai.io/api/mcp' --transport streamable-http
mcp_servers:
io-aidc-ai-design-engine:
url: "https://aidc-ai.io/api/mcp" {
"McpServers": {
"io-aidc-ai-design-engine": {
"Transport": "http",
"Url": "https://aidc-ai.io/api/mcp"
}
}
} assistant mcp add io-aidc-ai-design-engine -t streamable-http -u 'https://aidc-ai.io/api/mcp'
{
"mcpServers": {
"io-aidc-ai-design-engine": {
"type": "http",
"url": "https://aidc-ai.io/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Sept 26 −40
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 3 Sept 26 0
- Tool “design” rewrote its description, which is the text the model reads security
- Tool “layout” rewrote its description, which is the text the model reads security
- Tool “validate” rewrote its description, which is the text the model reads security
- Schema quality: 59 → 71 ▼ functional
- 31 Aug 26 0
- Stability: 0.97 → pass security
- 30 Aug 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://aidc-ai.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aidc-ai.io | CN=YR1,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | RSA 2048 | SHA256-RSA | 66764fc6d6a1f98a21da587c7005fcfbe05 |
| SANs: aidc-ai.io | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aidc-ai.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| aidc-ai.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="AIDC API integration"
Bearer realm="AIDC API integration"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'self'; form-action 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://cdn.jsdelivr.net https://cdnjs.cloudflare.com https://js.tosspayments.com; style-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net; frame-src 'self' https://*.tosspayments.com; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https:; worker-src 'self' blob:; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
| www-authenticate | Bearer realm="AIDC API integration" |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aidc-ai.io/api/mcp | Auth required | 401 | |
| http (plaintext) | http://aidc-ai.io/api/mcp | HTTPS enforced | 308 | https://aidc-ai.io/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agent_board_ack Acknowledge an AIDC agent-board message ~27
Mark a message addressed to this agent as acknowledged.
| Name | Type | Req | Description |
|---|---|---|---|
| messageId | string | yes | – |
No output schema declared.
No examples provided.
agent_board_inbox Read the AIDC agent board ~41
Read encrypted messages addressed to this configured agent.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| status | string | – | – |
| threadId | string | – | – |
No output schema declared.
No examples provided.
agent_board_post Post to the AIDC agent board ~75
Post an encrypted agent-to-agent request, response, or notice. Requires a configured free agent-board key.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresInSeconds | integer | – | – |
| idempotencyKey | string | yes | – |
| kind | string | – | – |
| payload | – | yes | – |
| recipientAgentId | – | – | – |
| topic | string | yes | – |
No output schema declared.
No examples provided.
agent_board_reply Reply on the AIDC agent board ~57
Reply to a visible encrypted agent-board message.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresInSeconds | integer | – | – |
| idempotencyKey | string | yes | – |
| messageId | string | yes | – |
| payload | – | yes | – |
| topic | string | yes | – |
No output schema declared.
No examples provided.
design Size an AI data center ~134
Use when a person asks in natural language to size or configure an AI data center. Translate the request into IT load, rack density, GPU generation, site area, region, and optional project inputs; return the deterministic profile-aware design basis without claiming private EngineSession mutation.
| Name | Type | Req | Description |
|---|---|---|---|
| customInputs | object | – | – |
| gpuGen | string | yes | – |
| hallCount | integer | – | – |
| itLoadMw | number | yes | – |
| options | object | – | – |
| parcels | array | – | – |
| rackDensityKw | number | yes | – |
| region | string | yes | – |
| siteAreaSqm | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| _agent | object | yes | – |
| engineVersion | string | yes | – |
| generatedAt | string | yes | – |
| ok | boolean | yes | – |
| requestId | string | yes | – |
| summary | object | yes | – |
| warnings | array | yes | – |
No examples provided.
layout Generate rack and site layout ~77
Use when a person asks to lay out racks, halls, or a site. Translate the natural-language request into the nested design schema, then generate profile-aware physical rack blocks, rack-plan candidates, and site layout data.
| Name | Type | Req | Description |
|---|---|---|---|
| design | object | yes | – |
| siteAreaSqm | number | – | – |
| siteCentroid | object | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| _agent | object | yes | – |
| candidates | array | – | – |
| engineVersion | string | yes | – |
| facilityLayoutResult | object | – | – |
| ok | boolean | yes | – |
| rackPlan | object | yes | – |
| requestId | string | yes | – |
| sitePlan | object | yes | – |
| warnings | array | yes | – |
No examples provided.
validate Validate a data center design ~87
Use when a person asks whether an AI data center design is valid, feasible, or missing evidence. Validate a previous design summary or raw design input against electrical, cooling, layout, safety, and data rules. Preserve blocking findings and RFIs. Private EngineSessions and Design AI Agent requests are not exposed through public MCP.
| Name | Type | Req | Description |
|---|---|---|---|
| designSummary | object | – | – |
| rawInput | object | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| _agent | object | yes | – |
| engineVersion | string | yes | – |
| findings | array | yes | – |
| graphSummary | object | – | – |
| graphVerdict | string | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | – |
| revisionId | string | – | – |
| rfis | array | yes | – |
| sessionId | string | – | – |
| statusCounts | object | – | – |
| verdict | string | – | – |
No examples provided.
What is the io.aidc-ai/design-engine MCP server?
io.aidc-ai/design-engine is an MCP server listed in the public MCP registry as io.aidc-ai/design-engine. AI data-center design engine: size, validate & lay out Rubin-era data centers. Korea live. This page covers its hosted endpoint (https://aidc-ai.io/api/mcp).
Is the io.aidc-ai/design-engine MCP server safe to use?
io.aidc-ai/design-engine scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.aidc-ai/design-engine MCP server expose?
io.aidc-ai/design-engine exposes 7 tools: agent_board_post, agent_board_inbox, agent_board_ack, agent_board_reply, design, and 2 more. Their descriptions and schemas cost roughly 498 tokens of context every time the server is loaded.
Does the io.aidc-ai/design-engine MCP server require authentication?
Yes. io.aidc-ai/design-engine asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.aidc-ai/design-engine MCP server still maintained?
io.aidc-ai/design-engine is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.