MCP server metadata for AI Design Blueprint Doctrine — remote endpoint at https://aidesignblueprint.com/mcp
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"aidesignblueprint-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# AI Design Blueprint — MCP Server <!-- mcp-name: io.github.aidesignblueprint/doctrine --> The industry standard doctrine for building safe, observable, and steerable AI agent UX. **Remote MCP endpoint:** `https://aidesignblueprint.com/mcp` ## Quick start Add to your MCP client config: ```json { "mcpServers": { "aidesignblueprint": { "url": "https://aidesignblueprint.com/mcp" } } } ``` ## What you get - **10 doctrine principles** across 4 principle clusters - **Curated implementation examples** with difficulty, library, and principle filters - **Application guides** for security hardening, observable evaluation, and more - **Agent asset artifacts** — `.mdc` rules files, `llms.txt`, skill packs ## Authentication tiers | Tier | Tools | Credential | |---|---|---| | Public | 13 tools | None required | | Auth | 6 tools | Firebase Bearer token | | Pro/Teams | 2 tools | Paid membership | ## Links - Site: [aidesignblueprint.com](https://aidesignblueprint.com) - Developer docs: [aidesignblueprint.com/en/for-agents](https://aidesignblueprint.com/en/for-agents) - Integrations: [github.com/aidesignblueprint/integrations](https://github.com/aidesignblueprint/integrations)
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.