AI Design Blueprint

warnings

aidesignblueprint.com

Public agentic AI doctrine tools plus authenticated architecture, design, and spec validators.

https://aidesignblueprint.com/mcpWebsiteOAuthMCP 2025-11-25v1.26.0last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 475 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://aidesignblueprint.com
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✕Not advertised
PKCE	✓S256
Grant types	authorization_code
Scopes	mcp
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Handshake succeeds; 29 tools listable
Credentials demanded in prose	✕me.coaching_context, me.sessions, me.validation_history, handoffs.operator These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.
Documentation	https://aidesignblueprint.com/for-agents/mcp

What the probe found

warningTools needing credentials are listed without a challenge

4 of the 29 tools listed anonymously say in their own descriptions that they need an account or a key (me.coaching_context, me.sessions, me.validation_history, handoffs.operator), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

29 tools usable without signing in

The server exposes a public surface before authorization: principles.list, clusters.list, principles.get, clusters.get, examples.get, principles.search, examples.search, assets.list, guides.list, guides.get, guides.search, signals.report, signals.feedback, architect.validate, design.validate, spec.validate, architect.validate_consensus, architect.certify, team.summarize, me.learning_path, me.coaching_context, me.add_evidence, me.sessions, me.session_event, me.await_steer, me.validation_history, handoffs.operator, handoffs.partnership, handoffs.agency.

Tools

architect.certifyarchitect.validatearchitect.validate_consensusassets.listclusters.getclusters.listdesign.validateexamples.getexamples.searchguides.getguides.listguides.searchhandoffs.agencyhandoffs.operatorhandoffs.partnershipme.add_evidenceme.await_steerme.coaching_contextme.learning_pathme.session_eventme.sessionsme.validation_historyprinciples.getprinciples.listprinciples.searchsignals.feedbacksignals.reportspec.validateteam.summarize

Contract history

24 Aug 2026v1.26.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/ai-design-blueprint/badge.svg)](https://mcpi.app/servers/ai-design-blueprint)