Design Check
Scores whether a page reads as AI-generated and names the tells to fix.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"designcheck": {
"url": "https://designcheck.allthepossibles.com/mcp"
}
}
}Remote endpoints
https://designcheck.allthepossibles.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (3)
🟢check_design(url, html)
Check a page's HTML/CSS/copy/interaction for the patterns that make AI-generated work read as generic: default fonts, soft tech gradients, pill+arrow buttons, eyebrow labels, a composition with no real width/background variation across sections, uniform card grids, copy tells (AI vocabulary, negative-parallel framing, hedge words, heavy em-dash use), and experience gaps (a diagnosis with no next step, dead-end links). Every finding includes a concrete fix. Call this before presenting UI to a human.
Input Schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "Page to fetch and check"
},
"html": {
"type": "string",
"description": "Raw HTML/CSS to check directly, if not fetching a URL"
}
}
}🟢check_copy(text)
Check marketing or outreach copy (an email, a landing-page draft, a pitch, a social post) for the tells that make it read as AI-generated: cliché vocabulary (delve, unlock, empower, seamlessly integrate, etc.), negative-parallel framing ("not just X, but Y"), hedge words, heavy em-dash use, and diagnosing a problem with no fix in the same breath. No page or markup needed, just the text. Call this before sending copy to a human.
Input Schema
{
"type": "object",
"properties": {
"text": {
"type": "string",
"description": "The raw copy to check"
}
},
"required": [
"text"
]
}🟢check_code(code)
Check a source file or diff for AI 'tells' left in comments: narrating fulfilling a request instead of describing the code ("as requested," "I've added," "here's the updated version") and hedge words. These reveal there was a conversation behind the change that a later reader has no access to. Call this before committing or shipping code an agent wrote.
Input Schema
{
"type": "object",
"properties": {
"code": {
"type": "string",
"description": "The source file or diff to check"
}
},
"required": [
"code"
]
}Community
Evidence