MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
AI Design Blueprint is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
29
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Doctrine and validators for governable agentic AI products.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ai-design-blueprint-mcp https://aidesignblueprint.com/mcp
# 2 — ask your agent for something these tools do
# principles.list, clusters.list, principles.get and 26 more
AI Design Blueprint costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ACAll 1 server
aidesignblueprint.com1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http ai-design-blueprint-mcp https://aidesignblueprint.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
29 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List Blueprint doctrine with stable slugs, titles, and clusters. The lens selects which of the three public doctrines: 'architecture' = the 10 agentic principles (default, the architect.validate rubric); 'surface' = the 8 experience-design laws (the design.validate rubric); 'spec' = the 8 spec-quality laws (the spec.validate rubric). Use this when you need the full inventory or want every entry in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cluster | no | Cluster slug to filter by (e.g. 'delegation', 'visibility', 'trust', 'orchestration'). Omit to return all principles. | |
| lens | string | no | Which public doctrine: 'architecture' = the 10 agentic principles (default), 'surface' = the 8 experience-design laws, 'spec' = the 8 spec-quality laws. |
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 or filtering principles.list by cluster. Prefer clusters.get when you already know the cluster slug and need full detail.
No parameter schema on file.
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 experience-design laws; 'spec' = one of the 8 spec-quality laws. Returns id, title, cluster, definition, rationale, implications, and risk-if-violated (laws also carry their eponym and validator_questions). Use this when you already have the ex
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Stable slug of the principle (e.g. 'establish-trust-through-inspectability'). |
| lens | string | no | Which public doctrine the slug belongs to: 'architecture' (10 principles, default), 'surface' (8 design laws), or 'spec' (8 spec laws). |
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 can pivot into principles.get without a second list call. WHEN TO CALL: the user has already named a specific cluster (e.g. 'delegation', 'visibility', 'trust', 'orchestration') OR you have a slug from a prior clusters.list / principles.list
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Stable slug of the principle cluster (e.g. 'delegation', 'visibility', 'trust', 'orchestration'). |
Get one curated example by stable slug. Returns title, summary, source-code links, principle coverage (the principle slugs the example demonstrates), difficulty, library/framework, and implementation notes. Use this when you already have the slug from examples.search, a principles.get response, or a guide cross-link; prefer examples.search when filtering by topic / principle / difficulty / library
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Stable slug of the curated example (e.g. 'agents-building-blocks-5-control'). |
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 challenge, failure mode, or keyword (e.g. 'reversibility', 'approval flow', 'delegation boundary'). Returns principle title, cluster, definition, rationale, and implementation heuristics. Prefer this over principles.list when you have a specifi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text search query matched against principle title, definition, rationale, and cluster. |
| limit | integer | no | Maximum number of results to return. Capped at server maximum. |
| lens | string | no | Which public doctrine to search: 'architecture' = the 10 agentic principles (default), 'surface' = the 8 experience-design laws, 'spec' = the 8 spec-quality laws, 'all' = all three. |
Search curated examples by free-text query, ranked by relevance, with optional filters: principle_ids (only examples covering those principles), difficulty (beginner/intermediate/advanced), library (e.g. 'langgraph', 'openai'). Returns each match's slug, title, summary, principle coverage, difficulty, library, and source-code link: slug is the handle examples.get hydrates. Default limit 5, capped
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text search query matched against example title, summary, and metadata. |
| principle_ids | no | Filter to examples that cover these principle IDs. | |
| difficulty | no | Filter by difficulty level. | |
| library | no | Filter by library or framework name (e.g. 'langgraph', 'openai', 'anthropic'). | |
| pattern_family | no | Filter to one agentic-pattern family. Implies patterns only, since no upstream cookbook example carries a family. | |
| limit | integer | no | Maximum number of results to return. Capped at server maximum. |
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 the Blueprint as native skill/rule files. Returns a list of assets with name, format (one of: zip / md / markdown / mdc / json / toml / text, the full vocabulary), pack_version, download_url, and platform target (Claude Code, Cursor, Codex
No parameter schema on file.
List application guides that show how Blueprint principles apply to engineering challenges (security, evaluation, observability, etc.). Use this to discover which guides exist before drilling in. Prefer guides.search when the user describes a topic or failure mode in natural language. Prefer guides.get when you already know the guide slug and need full detail.
No parameter schema on file.
Get a full application guide by its stable slug (e.g. 'security-application', 'observable-evaluation'). Returns sections, action items, and linked principles. Use this when you already have the guide slug from guides.list or guides.search. Prefer guides.search when the user describes a topic in natural language; prefer guides.list when you need the full inventory.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Stable slug of the application guide (e.g. 'security-application', 'observable-evaluation'). |
Search application guides by free-text query, matched against section answers and action items. Use this when the user describes an engineering challenge (security review, evaluation harness, observability) and wants matching guides. Prefer guides.get when you already have the guide slug; prefer guides.list when you need the full inventory.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text search query matched against all guide content including section answers and action items. |
| limit | integer | no | Maximum number of results to return. Capped at server maximum. |
Records a value moment (e.g. review_confidence, runtime_risk_found, workflow_clarity) after a successful validate run on any lens (architect.validate, design.validate, or spec.validate) or a doctrine session. Each event stores event_type, surface_used (mcp or the site section), perceived_value (1-5), and an optional short free-text note, brief_context (up to 500 characters). WHEN TO CALL: after ar
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_type | string | yes | Pick the type that best matches what just happened: 'review_confidence': a validator lens (architect.validate / design.validate / spec.validate) returned aligned; 'runtime_risk_found': a validate run |
| surface_used | no | Where the value was experienced. Use 'mcp' when called from Claude Code, Cursor, Windsurf, or any MCP client. Use 'principles' if the user was browsing or searching principles. Use 'examples' if the u | |
| brief_context | no | 1–2 plain-English sentences summarising what was helpful. Example: 'Validation identified a missing approval gate before email send.' No code snippets, no proprietary content, no user PII. Max 500 cha | |
| perceived_value | no | Ask the user: 'On a scale of 1–5, how valuable was this session?' Map their answer directly: 1=low, 5=high. Do not guess: only set this if the user gave an explicit score. | |
| workflow_stage | no | Infer from what the user was doing: 'exploring': reading doctrine, browsing principles; 'designing': planning architecture or agent flows; 'implementing': writing or refactoring code; 'reviewing': run | |
| would_recommend | no | Ask the user: 'Would you recommend the Blueprint to a colleague?' Set true/false based on their answer. Only set if asked: do not assume. | |
| team_size | no | If the user mentions their team size during the session, record it here. Do not ask for it explicitly: only capture if volunteered. |
Public: records explicit free-text user feedback about the Blueprint, this tool surface, or a specific principle/example. Captures category (bug, doctrine_critique, missing_example, ergonomics, other), free-text body, and optional contact_email when permission_to_follow_up is true. WHEN TO CALL: ONLY when the user explicitly says they want to give feedback (e.g. 'can you log this as feedback', 'fi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_type | no | What the user was doing when they decided to give feedback. Use plain English: e.g. 'code-review', 'architecture-design', 'agent-setup', 'onboarding', 'validation'. Infer from context. | |
| surface | no | Which Blueprint surface the feedback is about. Use 'mcp' if the session was via Claude Code or another MCP client. Use 'principles', 'examples', 'guides', 'coaching', or 'validation' based on what the | |
| rating_clarity | no | Ask the user: 'How clear was the Blueprint guidance? Rate 1–5.' 1 = very unclear, 5 = very clear. Only set if the user gives an explicit number. | |
| rating_usefulness | no | Ask the user: 'How useful was the Blueprint for this task? Rate 1–5.' 1 = not useful, 5 = very useful. Only set if the user gives an explicit number. | |
| what_helped | no | Ask the user: 'What was most helpful?' Record their answer verbatim or paraphrased in plain English. Max 1000 chars. No code snippets, no proprietary content. | |
| what_missing | no | Ask the user: 'What was missing or could be improved?' Record their answer verbatim or paraphrased. Max 1000 chars. | |
| would_use_again | no | Ask the user: 'Would you use the Blueprint again for a similar task?' Set true/false based on their answer. Only set if they answer explicitly. | |
| contact_email | no | Only ask for this if the user explicitly says they want a follow-up response. Never prompt for email unprompted. Only stored when permission_to_follow_up=true. | |
| permission_to_follow_up | boolean | no | Set to true only if the user explicitly said they want a follow-up. Must be confirmed before storing contact_email. |
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. Long-running LLM call (60-180s typical); MCP clients commonly close the call before the server returns. Retrying re-runs the 60-180s LLM call from scratch and burns compute. RECOVERY: the run_id is emitted in the FIRST notifications/progre
| Parameter | Type | Required | Notes |
|---|---|---|---|
| implementation_context | string | yes | The artifact under review. SEND FULL FILE CONTENTS VERBATIM: the architect cites per-line evidence (identifiers, branch ordering, structural choices); any compression destroys evidence and produces ha |
| focus_area | no | Narrow the evaluation to a specific principle cluster or slug (e.g. 'delegation', 'visibility', 'establish-trust-through-inspectability'). | |
| task | no | What the agent or workflow is trying to accomplish. Adds evaluation context. | |
| language | no | Programming language of the code being evaluated (e.g. 'python', 'typescript'). | |
| repository | no | Iteration key. SAME value across calls auto-resolves the most recent prior run as prior_run_baseline for iteration-aware grading (per-principle severity deltas, regressions/improvements). CHANGING t | |
| files | no | List of file paths relevant to the implementation context. | |
| goals | no | Specific safety or quality goals to evaluate against (e.g. 'prevent irreversible actions', 'explicit approvals'). | |
| example_limit | integer | no | Maximum number of curated examples to include in recommendations. |
| private_session | boolean | no | Set to true to skip the stored run AND prior-run anchoring AND run_id recovery for this call. Operational security and cost logs are still kept, per the Privacy Policy. The request is also not persist |
| session_id | no | Optional Governed Session to attach this run to (GEP-M2). Must reference a session YOU own (list via me.sessions; sessions are created in the web app at /app/sessions): foreign ids are refused before |
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 surface-craft companion to architect.validate: where architect.validate scores agentic ARCHITECTURE against the 10 agentic principles, design.validate scores the PERCEPTIBLE SURFACE, what the user sees, taps, scans, and remembers (Jakob's familia
| Parameter | Type | Required | Notes |
|---|---|---|---|
| implementation_context | string | yes | The frontend artefact under review. SEND FULL SOURCE VERBATIM: the reviewer cites specific elements, values, and structure; any compression destroys evidence and produces findings on code that isn't t |
| task | no | What this surface is for (e.g. 'the closed-beta apply form'). Adds evaluation context. | |
| goals | no | Specific craft/UX goals to weight (e.g. 'WCAG 2.2 AA', 'one primary action per screen'). | |
| files | no | File paths relevant to the artefact, for context. | |
| repository | no | Project/repository key. Groups this run with prior design.validate runs on the same project in your validation-history dashboard (the same grouping architect.validate uses), under the 'surface' dimens | |
| private_session | boolean | no | Set true to skip the stored run AND run_id recovery (operational security and cost logs are still written) for this call (a private one-shot that does not appear in the dashboard). The request is also |
| session_id | no | Optional Governed Session to attach this run to (GEP-M2). Must reference a session YOU own (list via me.sessions; sessions are created in the web app at /app/sessions): foreign ids are refused before |
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 laws of the Spec Quality Blueprint. The what-to-build lens of the doctrine trio, applied BEFORE code exists: where architect.validate scores built agentic ARCHITECTURE and design.validate scores the rendered SURFACE, spec.validate scores the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| implementation_context | string | yes | The specification under review. SEND FULL TEXT VERBATIM: the reviewer cites specific requirements, decisions, and tasks; any compression destroys evidence and produces findings on content that isn't t |
| task | no | What this spec is for (e.g. 'the closed-beta apply flow rework'). Adds evaluation context. | |
| goals | no | Specific quality goals to weight (e.g. 'ready for an agent to build unattended', 'tight scope'). | |
| files | no | File paths relevant to the spec, for context. | |
| repository | no | Project/repository key. Groups this run with prior spec.validate runs on the same project in your validation-history dashboard (the same grouping the other lenses use), under the 'spec' dimension. | |
| private_session | boolean | no | Set true to skip the stored run AND run_id recovery (operational security and cost logs are still written) for this call (a private one-shot that does not appear in the dashboard). The request is also |
| session_id | no | Optional Governed Session to attach this run to (GEP-M2). Must reference a session YOU own (list via me.sessions; sessions are created in the web app at /app/sessions): foreign ids are refused before |
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 clients often close the call before the server returns. Retrying re-runs N × 60-180s LLM calls from scratch and burns N× compute. RECOVERY: same heartbeat pattern as architect.validate, the run_id is emitted in the FIRST progress event at t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| implementation_context | string | yes | The artifact under review. SEND FULL FILE CONTENTS VERBATIM: same constraint as architect.validate. Truncation produces hallucinated findings on code that isn't there. |
| focus_area | no | Optional: narrow the review to a principle cluster or slug. | |
| task | no | What the agent or workflow is trying to accomplish. | |
| language | no | Programming language of the code (e.g. 'python'). | |
| repository | no | Iteration key. Consensus children all run unanchored (private_session=True), but the consolidated row IS persisted under this key: discoverable as prior baseline for the next single-shot `architect. | |
| files | no | List of file paths relevant to the implementation. | |
| goals | no | Specific safety or quality goals to evaluate against. | |
| example_limit | integer | no | Max curated examples per child run. |
| n | integer | no | Number of parallel child runs. Default 3 (the variance signal is visible at N=3; cost = 3× LLM bill). Capped server-side by Settings.consensus_n_max (default 5). |
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 RETRY THIS TOOL. RECOVERY FIRST: the run_id is emitted in the FIRST notifications/progress event at t=0s (BEFORE the LLM call begins). Capture it. On timeout, call me.validation_history(run_id='<that-id>') to fetch the persisted cert v
| Parameter | Type | Required | Notes |
|---|---|---|---|
| run_id | string | yes | The run_id from a prior architect.validate call. Returned in the validate response when persistence_status='saved'. Must be owned by the caller (per-user authorisation, same gate as me.validation_hist |
| code | string | no | The same code that was sent to architect.validate to produce this run_id. Sent verbatim: the cert reviewer needs the actual code to surface production_blockers the first pass missed. May be omitted (e |
Teams/Enterprise: summarises the caller's tool-usage patterns and value signals over a configurable window (default 30 days). Returns period_days, most_used_tools (call counts and average latency), value_events by event_type, observed_usage_stage, validator_lenses_used, recommended_next_assets and private_session. WHEN TO CALL: the user asks 'how is the Blueprint helping me/my team', 'what should
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days_back | integer | no | Number of days of usage history to include in the summary. |
| private_session | boolean | no | No effect on this tool: accepted only so clients can pass the same flag to every tool. This read stores no run, and the per-call tool-usage record is written on every call. |
Authenticated: returns the caller's Blueprint learning-path state: current course slug, stage progress, certification status (Foundation, Practitioner, Capstone), Capstone track eligibility flags, and the next recommended stage. WHEN TO CALL: the user asks 'where am I', 'what's next', or 'am I Capstone-eligible'; before suggesting next-step coaching content. WHEN NOT TO CALL: as a heartbeat (state
No parameter schema on file.
Authenticated: returns stages in the caller's active course where recorded evidence is thin relative to the stage's principle requirements. Each thin stage carries the missing principle slugs + a short diagnostic so the caller can suggest the user record concrete evidence. WHEN TO CALL: when the user asks 'what should I work on next' or 'what's weak in my Blueprint progress'; before suggesting whi
No parameter schema on file.
Authenticated: append a free-text evidence note to a specific stage in the caller's active course. Notes record concrete implementation observations, decisions, or artefacts that demonstrate progress through a Blueprint principle (e.g. how a delegation boundary was implemented, what approval flow was chosen and why). Persisted as UserStageEvidence rows scoped to (user_id, course_slug, stage_slug).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| course_slug | string | yes | Slug of the course the stage belongs to (e.g. 'agentic-fundamentals'). |
| stage_id | string | yes | ID of the stage to append the evidence note to. |
| note | string | yes | Evidence note to append to the delegation boundary notes for this stage. |
Pro/Teams: list or inspect the authenticated user's Governed Sessions (GEP-M2): durable, owner-scoped containers that group validation runs across lenses (architect.validate → 'architecture', design.validate → 'surface', spec.validate → 'spec') into one timeline for one piece of work. Two modes: (1) No arguments returns every session (id, title, status, repo_url, spec_ref, team_agents, run_count,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | no | Session id to inspect (returns the session + its run timeline). Owner-scoped: ids you don't own answer 'Session not found.'. Omit to list all your sessions. |
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 role lenses, pushbacks, plan previews, gates, and acks land as structured events next to the validation runs, so the session reads as a system, not a transcript. CHANNEL PROVENANCE: this MCP channel posts the AGENT-SIDE vocabulary only. `s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | integer | yes | The Governed Session to post to. Must be YOURS and have team_agents enabled; list sessions via me.sessions. |
| event_type | string | yes | handoff | pushback | plan_preview | gate | ack (ack = started working on a steer; steer itself is AIDB Studio-only and refused on this channel) |
| actor | string | yes | Who acted: pm | engineer | designer | system (human is reserved for AIDB Studio) |
| summary | string | yes | One-to-two sentence event summary (truncated to 500 chars): a decision or transition, not a chat message. |
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 cursor read against the session log is authoritative (at-least-once: a lost response is safely re-issuable with the same cursor, and timed_out is only returned after a final confirming read). The in-between wake-up is a best-effort in-process
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | integer | yes | The Governed Session to watch. Must be YOURS and have team_agents enabled; list sessions via me.sessions. |
| after_event_id | integer | no | Cursor: highest session-event id you have already seen (0 = deliver any existing steer). Pass the value from your previous await_steer result or me.sessions read. Non-destructive at-least-once deliver |
| timeout_s | integer | no | Seconds to wait before returning timed_out. Clamped to 5-240, DEFAULT 45: safe under Claude Code's 60-second first-response-byte timer for HTTP servers. Longer waits require the per-server timeout rai |
Pro/Teams: return the authenticated user's validation run history for all three lenses (architect.validate → validator='architecture', design.validate → validator='surface', spec.validate → validator='spec') with the Blueprint Readiness Score (0-100), letter grade (A-F), and tier (draft, emerging, production_ready). Each run carries a validator field naming its lens. Three lookup modes: (1) `run
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repository | no | Repository name or path to scope the history to. Pass the same value you would pass to architect.validate. Omit to get one summary per repository. Mutually exclusive with run_id: if both are passed, | |
| run_id | no | Single-run lookup by run_id (UUID). Returns the persisted result_json verbatim: the same payload architect.validate would have returned if your client hadn't timed out. Use this to recover a result wh | |
| limit | integer | no | Maximum number of runs to return when scoped to a single repository. Capped at 50. Ignored when run_id is provided. |
Authenticated: creates a support handoff record when an agent needs human review, account-specific escalation, or operator follow-up that cannot be resolved with the read-only doctrine tools. Persists a SupportHandoff row (reason, topic, page_url, agent_name, agent_platform, trace_summary, user_email) routed to the support inbox; user is contacted by the team. WHEN TO CALL: user explicitly asks fo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reason | string | yes | Clear description of why a human operator review is needed. |
| topic | string | no | Topic category for routing (e.g. 'agent', 'billing', 'access', 'general'). |
| page_url | no | URL of the page or context where the handoff was triggered. | |
| agent_name | string | no | Name of the agent or client triggering the handoff. |
| agent_platform | no | Platform or runtime the agent is running on (e.g. 'claude-code', 'cursor', 'copilot'). | |
| trace_summary | no | Optional summary of the agent's recent actions or trace for operator context. | |
| locale | string | no | Response locale for the handoff acknowledgment. |
Authenticated: creates a partnerships handoff record for design-partner, ecosystem, training, or advisory conversations needing human review. Persists a PartnershipHandoff row routed to the partnerships inbox; the user is contacted by the team. WHEN TO CALL: user explicitly wants to engage as a design partner, co-marketing/training partner, or evaluate the Blueprint for their org's training progra
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reason | string | yes | Clear description of the partnership opportunity or inquiry. |
| topic | string | no | Partnership topic category. |
| organization | no | Name of the organization or company making the partnership inquiry. | |
| role | no | Role or title of the person submitting the partnership inquiry. | |
| website | no | Website of the organization for additional context. | |
| agent_name | string | no | Name of the agent or client triggering the handoff. |
| agent_platform | no | Platform or runtime the agent is running on. | |
| trace_summary | no | Optional agent trace summary for operator context. | |
| locale | string | no | Response locale for the handoff acknowledgment. |
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 inbox; the user is contacted by the team for a scoped proposal. Engagement scopes: workflow sprint (rapid agentic workflow implementation), proof-of-concept (validate a specific agent design in a bounded timeframe), pilot support (co-design
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reason | string | yes | Description of the engagement need: workflow sprint, proof-of-concept, pilot support, or advisory. |
| company | no | Company or team name submitting the agency inquiry. | |
| role | no | Role or title of the person submitting the agency inquiry. | |
| workflow_stage | no | Current workflow stage. | |
| support_type | no | Type of support needed. | |
| website | no | Website or relevant URL for the team or project. | |
| agent_name | string | no | Name of the agent or client triggering the handoff. |
| agent_platform | no | Platform or runtime the agent is running on. | |
| trace_summary | no | Optional agent trace summary for operator context. | |
| locale | string | no | Response locale for the acknowledgment. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install AI Design Blueprint or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.26.0.
1.26.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish AI Design Blueprint can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.