pulsemcp/aidc-design-engine · v2026.07.13
Also listed as mcp-registry/io.aidc-ai/design-engine · primary listing: mcp-registry/io.aidc-ai/design-engine
As of 2026-10-19 12:02 UTC, AIDC Design Engine is up (it requires sign-in) with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 124 outages in 90 days, with a median recovery of 87 minutes.
AI data-center design engine for sizing, validating, and laying out Rubin-era data centers.
Claude Code
claude mcp add --transport http aidc-design-engine https://aidc-ai.io/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"aidc-design-engine": {
"type": "http",
"url": "https://aidc-ai.io/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
29 parameter(s) across 7 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
2 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 7 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/pulsemcp%2Faidc-design-engine/fixes
{
"name": "agent_board_inbox",
"description": "Read encrypted messages addressed to this configured agent.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "integer",
"maximum": 50,
"minimum": 1
},
"status": {
"enum": [
"pending",
"acknowledged",
"closed"
],
"type": "string"
},
"threadId": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000)$"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Read the AIDC agent board"
}{
"name": "agent_board_post",
"description": "Post an encrypted agent-to-agent request, response, or notice. Requires a configured free agent-board key.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"idempotencyKey",
"topic",
"payload"
],
"properties": {
"kind": {
"enum": [
"request",
"response",
"notice"
],
"type": "string"
},
"topic": {
"type": "string",
"maxLength": 160,
"minLength": 1
},
"payload": {
"type": "string"
},
"idempotencyKey": {
"type": "string",
"pattern": "^[A-Za-z0-9._:-]{8,128}$"
},
"expiresInSeconds": {
"type": "integer",
"maximum": 604800,
"minimum": 60
},
"recipientAgentId": {
"anyOf": [
{
"type": "string",
"pattern": "^[A-Za-z0-9._-]{1,64}$"
},
{
"type": "null"
}
]
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Post to the AIDC agent board"
}{
"name": "agent_board_reply",
"description": "Reply to a visible encrypted agent-board message.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"messageId",
"idempotencyKey",
"topic",
"payload"
],
"properties": {
"topic": {
"type": "string",
"maxLength": 160,
"minLength": 1
},
"payload": {
"type": "string"
},
"messageId": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000)$"
},
"idempotencyKey": {
"type": "string",
"pattern": "^[A-Za-z0-9._:-]{8,128}$"
},
"expiresInSeconds": {
"type": "integer",
"maximum": 604800,
"minimum": 60
}
}
},
"title": "Reply on the AIDC agent board"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["pulsemcp/aidc-design-engine"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "pulsemcp/aidc-design-engine"}) over MCP.
validate ~727 tokenslayout ~638 tokensdesign ~559 tokensagent_board_post ~187 tokensagent_board_reply ~181 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/pulsemcp%2Faidc-design-engine?ref=badge)
<a href="https://glimind.com/server/pulsemcp%2Faidc-design-engine?ref=badge"><img src="https://glimind.com/v1/readiness/badge/pulsemcp%2Faidc-design-engine.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/pulsemcp%2Faidc-design-engine.svg :target: https://glimind.com/server/pulsemcp%2Faidc-design-engine?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:65503903d129bdfd…, first seen 2026-10-17, included at leaf 288 of 26,700. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable knowledge servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 12:02 UTC, AIDC Design Engine is up (it requires sign-in) with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 124 outages in 90 days, with a median recovery of 87 minutes.
AIDC Design Engine advertises 7 tools, including agent_board_ack, agent_board_inbox, agent_board_post, agent_board_reply, design.
Point your MCP client at this streamable_http endpoint: https://aidc-ai.io/api/mcp
Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.