Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TheDesignAgent

REMOTE · WWW.THEDESIGNAGENT.AI · 2 COMPONENTS

A design agent in your coding agent's loop: briefs each screen, reviews UX and visual quality.

0 this week 38 Trust /100

Last scanned (8 hours ago)

Scores higher than 32% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security94
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 8 Oct 26 −34
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Stability: 0.07 → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: partial → pass ▲ security
    • First check of Authorization: partial security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 5 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Oct 26 +10
    • Authorization: unverified → partial ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • MCP protocol: fail → pass ▲ functional
    • First check of Tool coverage: 100 functional
  • 3 Oct 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Oct 2026 · Probed https://www.thedesignagent.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.thedesignagent.ai CN=YR1,O=Let's Encrypt,C=US 20 Sept 2026 19 Dec 2026 RSA 2048 SHA256-RSA 5fdba28f157ce2ce95ff1053744497d33e0
SANs: www.thedesignagent.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.thedesignagent.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
thedesignagent.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer resource_metadata="https://www.thedesignagent.ai/.well-known/oauth-protected-resource/mcp"

Bearer resource_metadata="https://www.thedesignagent.ai/.well-known/oauth-protected-resource/mcp"
Header Value
strict-transport-security max-age=63072000
www-authenticate Bearer resource_metadata="https://www.thedesignagent.ai/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://www.thedesignagent.ai/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://www.thedesignagent.ai/mcp
Authorisation server https://bxqifcmkydlsgwgcpqda.supabase.co/auth/v1

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.thedesignagent.ai/mcp Auth required 401
http (plaintext) http://www.thedesignagent.ai/mcp HTTPS enforced 308 https://www.thedesignagent.ai/mcp
MCP tools · 3 exposed · ~890 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
Discover ~401

Get a build brief calibrated to your project, persona, and the specific screen you're building. Call this BEFORE building any screen. Returns: - The active Job-to-be-Done for the task - Relevant heuristics, cognitive guidance, and patterns from the corpus - A focused build brief (~600 tokens) to inject into your build context CALL LIFECYCLE: - First call for a new project (no project_id): returns _meta.tda_status='setup_required' with an extraction task. Scan the repo's schema/types/migrations (or, with no repo, ask the user for a short product description as the task explains) and resubmit with project_model populated. - Subsequent calls: send ONLY task + project_id. project_model is cached server-side from the first call; resending it wastes ~2–4k tokens per call and re-runs validation. Resend project_model ONLY when a response returns _meta.tda_status='setup_required' or 'model_stale'. Use project_id from .thedesignagent or memory across calls. Pass repo_hash (SHA256 of git remote origin URL) only as a fallback if no project_id is known yet.

NameTypeReqDescription
codebase_contextstring–Surrounding code snippet for context
project_idstring–project_id from .thedesignagent file
project_modelobject–Project model. Send ONLY on first call (no project_id yet) OR when a prior response returned _meta.tda_status="setup_required" or "model_stale". Do NOT resend on routine subsequent calls — it is cach…
repo_hashstring–SHA256 of git remote origin URL
schema_hashstring–SHA256 of schema/type files — triggers model refresh if stale
skillsarray–Per-call skill selection (overrides project defaults)
taskstringyesDescribe the screen you're about to build
NameTypeReqDescription
project_idstring–Persist in .thedesignagent and send on later calls
retry_okbooleanyesWhether the same call can safely be retried
scorenumber–Overall 0–10 score (Ux and Visual)
statusstringyeshealthy | degraded:stage3 | degraded:other | setup_required | model_stale | local_install_required | login_required | auth_failed | insufficient_credits | rate_limited | pipeline_error

No examples provided.

Ux ~254

Evaluate a built UI artifact for JTBD fit, heuristic compliance, cognitive load, and pattern conformance. Call this AFTER building a screen. TheDesignAgent scores: - Heuristics: violations against Nielsen's heuristics + project-specific anti-patterns - Cognitive: load profile against the stored persona - Patterns: conformance to established project pattern decisions - JTBD fit: does the artifact serve the resolved job? Returns ux_score (0–10) + findings + prioritised recommendations. Stores new anti-patterns to project context — future builds benefit automatically.

NameTypeReqDescription
artifactstringyesThe UI description or component code to evaluate
codebase_contextstring–Optional surrounding code context
project_idstring–project_id from .thedesignagent file in project root
repo_hashstring–SHA256 of git remote origin URL (fallback if no .thedesignagent)
routestring–URL path of the page under review, e.g. /orders. Reviews judge it against that page's own job.
stagesarray–Run only named stages (omit to run all)
taskstringyesDescribe the workflow or screen you're building
NameTypeReqDescription
project_idstring–Persist in .thedesignagent and send on later calls
retry_okbooleanyesWhether the same call can safely be retried
scorenumber–Overall 0–10 score (Ux and Visual)
statusstringyeshealthy | degraded:stage3 | degraded:other | setup_required | model_stale | local_install_required | login_required | auth_failed | insufficient_credits | rate_limited | pipeline_error

No examples provided.

Visual ~235

Evaluate a built UI artifact for visual design quality — brand compliance, visual cognitive load, and aesthetic quality. Pass render_url to review a real screenshot. This hosted server screenshots public pages and preview deploys (pass vercel_bypass_token for a protected Vercel preview). It cannot reach localhost or private networks: for those, it returns instructions for the local MCP server. With no render_url, the review runs from the artifact code alone. If the page redirects to login, no review runs and nothing is charged.

NameTypeReqDescription
artifactstringyesThe UI description or component code to evaluate
project_idstring–project_id from .thedesignagent file in project root
render_urlstring–Public or preview URL to screenshot, e.g. https://my-app-git-feature.vercel.app/checkout
repo_hashstring–SHA256 of git remote origin URL
taskstringyesDescribe the workflow or screen you're building
vercel_bypass_tokenstring–Optional. Vercel 'Protection Bypass for Automation' secret, for a protected preview deploy.
NameTypeReqDescription
project_idstring–Persist in .thedesignagent and send on later calls
retry_okbooleanyesWhether the same call can safely be retried
scorenumber–Overall 0–10 score (Ux and Visual)
statusstringyeshealthy | degraded:stage3 | degraded:other | setup_required | model_stale | local_install_required | login_required | auth_failed | insufficient_credits | rate_limited | pipeline_error

No examples provided.

Install

How do I install the TheDesignAgent MCP server?

TheDesignAgent is a hosted endpoint at https://www.thedesignagent.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.thedesignagent.ai

# add to Claude Code
claude mcp add --transport http ai-thedesignagent-mcp 'https://www.thedesignagent.ai/mcp'
Common questions

What is the TheDesignAgent MCP server?

TheDesignAgent is an MCP server listed in the public MCP registry as ai.thedesignagent/mcp. A design agent in your coding agent's loop: briefs each screen, reviews UX and visual quality. This page covers its hosted endpoint (https://www.thedesignagent.ai/mcp).

Is the TheDesignAgent MCP server safe to use?

TheDesignAgent scores 38 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the TheDesignAgent MCP server expose?

TheDesignAgent exposes 3 tools: Discover, Ux, Visual. Their descriptions and schemas cost roughly 890 tokens of context every time the server is loaded.

Does the TheDesignAgent MCP server require authentication?

Yes. TheDesignAgent asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the TheDesignAgent MCP server still maintained?

TheDesignAgent is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.