# Aidesignblueprint Blueprint MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.aidesignblueprint%2Fblueprint
Registry id: `mcp-registry/com.aidesignblueprint/blueprint`
Status: live (checked 2026-10-27T16:09:31.879Z)

## Verdict

Aidesignblueprint Blueprint MCP server answered 99.96% of Glimind's liveness checks over 30 days, better than 35% of MCP servers, with 746 ms median handshake and 18 outages in 90 days. Its agent-readiness grade is A (90/100) across 29 tools, costing an agent about 12,906 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.96% | 35% of MCP servers |
| Median handshake latency | 746 ms | 27% of MCP servers |
| p95 handshake latency | 2916 ms | — |
| Checks in 30 days | 5,025 | — |
| Outages, 90 days | 18 | — |
| Median recovery | 2 min | — |
| Agent-readiness score | 90/100 (A) | 69% of MCP servers |
| Tools | 29 | — |
| Tool-list size for an agent | ~12,906 tokens | 15% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "aidesignblueprint-blueprint-mcp-server": {
      "type": "http",
      "url": "https://aidesignblueprint.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http aidesignblueprint-blueprint-mcp-server https://aidesignblueprint.com/mcp
```

## Tools (29)

- `architect.certify`: Pro/Teams: second-pass adversarial certification of an architect.validate run that scored production_ready (A or B first-pass tier). ON CLIENT TIMEOUT: DO NOT R
- `architect.validate`: Pro/Teams: first-pass doctrine review of agentic code/workflow against the 10-principle AI Design Blueprint doctrine. ON CLIENT TIMEOUT: DO NOT RETRY THIS TOOL.
- `architect.validate_consensus`: Pro/Teams: N-shot CONSENSUS doctrine review of agentic code. ON CLIENT TIMEOUT: DO NOT RETRY THIS TOOL. Long-running (~80-120s for N=3 parallel LLM calls); MCP 
- `assets.list`: Public: list downloadable doctrine and agent asset artifacts (skill packs, rule packs, MCP setup snippets) the user can drop into their AI coding tool to import
- `clusters.get`: Get one principle cluster by stable slug. Returns the cluster definition, shared rationale, and the full set of member principles (slug + title) so the caller c
- `clusters.list`: List all principle clusters with their stable slugs and linked principle titles. Use this to discover which clusters exist before drilling in with clusters.get 
- `design.validate`: Pro/Teams: first-pass surface-craft review of a FRONTEND artefact (component, screen, or flow) against the 8 laws of the Experience Design Blueprint. The surfac
- `examples.get`: Get one curated example by stable slug. Returns title, summary, source-code links, principle coverage (the principle slugs the example demonstrates), difficulty
- `examples.search`: Search curated examples by free-text query, ranked by relevance, with optional filters: principle_ids (only examples covering those principles), difficulty (beg
- `guides.get`: Get a full application guide by its stable slug (e.g. 'security-application', 'observable-evaluation'). Returns sections, action items, and linked principles. U
- `guides.list`: List application guides that show how Blueprint principles apply to engineering challenges (security, evaluation, observability, etc.). Use this to discover whi
- `guides.search`: Search application guides by free-text query, matched against section answers and action items. Use this when the user describes an engineering challenge (secur
- `handoffs.agency`: Authenticated: submit an agency engagement enquiry on behalf of the caller for a founder-led discovery call. Persists an AgencyHandoff row routed to the agency 
- `handoffs.operator`: Authenticated: creates a support handoff record when an agent needs human review, account-specific escalation, or operator follow-up that cannot be resolved wit
- `handoffs.partnership`: Authenticated: creates a partnerships handoff record for design-partner, ecosystem, training, or advisory conversations needing human review. Persists a Partner
- `me.add_evidence`: Authenticated: append a free-text evidence note to a specific stage in the caller's active course. Notes record concrete implementation observations, decisions,
- `me.await_steer`: Pro/Teams. BLOCK until the session owner posts the next `steer` event to a Governed Session from AIDB Studio, then return it. DELIVERY GUARANTEE: the durable cu
- `me.coaching_context`: Authenticated: returns stages in the caller's active course where recorded evidence is thin relative to the stage's principle requirements. Each thin stage carr
- `me.learning_path`: Authenticated: returns the caller's Blueprint learning-path state: current course slug, stage progress, certification status (Foundation, Practitioner, Capstone
- `me.session_event`: Pro/Teams: append a TYPED TEAM EVENT to a Governed Session's timeline (GEP-M6). This is how the user's own harness makes trio work inspectable: handoffs between
- `me.sessions`: Pro/Teams: list or inspect the authenticated user's Governed Sessions (GEP-M2): durable, owner-scoped containers that group validation runs across lenses (archi
- `me.validation_history`: Pro/Teams: return the authenticated user's validation run history for all three lenses (architect.validate → validator='architecture', design.validate → validat
- `principles.get`: Get one doctrine entry by stable slug. The lens selects the doctrine: 'architecture' = one of the 10 agentic principles (default); 'surface' = one of the 8 expe
- `principles.list`: List Blueprint doctrine with stable slugs, titles, and clusters. The lens selects which of the three public doctrines: 'architecture' = the 10 agentic principle
- `principles.search`: Search Blueprint principles by free-text query and return the closest matches ranked by relevance. Use this to find principles related to a specific design chal
- `signals.feedback`: Public: records explicit free-text user feedback about the Blueprint, this tool surface, or a specific principle/example. Captures category (bug, doctrine_criti
- `signals.report`: Records a value moment (e.g. review_confidence, runtime_risk_found, workflow_clarity) after a successful validate run on any lens (architect.validate, design.va
- `spec.validate`: Pro/Teams: first-pass specification-quality review of a WRITTEN SPEC (proposal, design doc, task breakdown, or an OpenSpec-style change bundle) against the 8 la
- `team.summarize`: Teams/Enterprise: summarises the caller's tool-usage patterns and value signals over a configurable window (default 30 days). Returns period_days, most_used_too

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.