mcp-registry/com.allthepossibles/designers · v1.0.0
As of 2026-10-26 17:58 UTC, the Allthepossibles Designers MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Checks, prompts and skills for designers working with AI: contrast, a11y, heuristics, critique.
Point your MCP client at this streamable-http endpoint: https://designers.allthepossibles.com/mcp
141 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
16 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
2 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Loading this server's tool list costs an agent ~35,431 tokens before any work — more than 99% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.allthepossibles%2Fdesigners/fixes
{
"name": "modular_scale",
"description": "Build a modular type scale. Pass `base` (px, default 16) and `ratio` (a number from 1.01 to 4, or a name: minor second, major second, minor third, major third, perfect fourth, augmented fourth, perfect fifth, golden, major sixth, octave; default major third 1.25). Optional: `stepsUp` (default 6), `stepsDown` (default 2), `rootPx` (default 16), `minViewport` and `maxViewport` (defaults 320 and 1280), `minBase` and `minRatio` for the small-screen end of the fluid scale (default: same base, ratio p",
"inputSchema": {
"type": "object",
"properties": {
"base": {
"type": "number",
"description": "Body size in px (8 to 64, default 16)."
},
"ratio": {
"description": "A number (1.01 to 4) or a name such as \"major third\", \"perfect fourth\", \"golden\". Default major third.",
"type": "string"
},
"rootPx": {
"type": "number",
"description": "Root font size for rem conversion (default 16)."
},
"minBase": {
"type": "number",
"description": "Base size at the small viewport (default same as base)."
},
"stepsUp": {
"type": "integer",
"description": "Steps above the base (0 to 12, default 6)."
},
"minRatio": {
"description": "Ratio at the small viewport, number or name (default: 20 percent closer to 1 than ratio).",
"type": "string"
},
"stepsDown": {
"type": "integer",
"description": "Steps below the base (0 to 6, default 2)."
},
"maxViewport": {
"type": "number",
"description": "Viewport width in px where the fluid scale reaches full size (default 1280)."
},
"minViewport": {
"type": "number",
"description": "Viewport width in px where the fluid scale uses its small values (default 320)."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
},
"title": "Modular type scale"
}{
"name": "plan_usability_test",
"description": "Build a usability test plan skeleton with fixed template logic (no model call). Pass `goal` (what you need to learn), `participants` (a number, a list of criteria, or {count, groups, profile}) and `tasks` (strings, or {name, scenario, start, success}). Optional: `product`, `method` (moderated or unmoderated), `session_minutes`. Returns a screener built from your criteria, a session outline, each task checked for leading wording (naming buttons or menus, 'click', 'easily') with a scenario shape, ",
"inputSchema": {
"type": "object",
"required": [
"goal",
"tasks"
],
"properties": {
"goal": {
"type": "string",
"description": "What the study needs to learn."
},
"tasks": {
"type": "array",
"items": {},
"description": "Task strings or {name, scenario, start, success}."
},
"method": {
"enum": [
"moderated",
"unmoderated"
],
"type": "string"
},
"product": {
"type": "string"
},
"participants": {
"description": "Number, list of criteria, or {count, groups, profile}.",
"type": "string"
},
"session_minutes": {
"type": "number",
"description": "Session length, default 45."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
},
"title": "Usability test plan"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.allthepossibles/designers"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.allthepossibles/designers"}) over MCP.
plan_breakpoints ~451 tokensusability_stats ~444 tokensmodular_scale ~429 tokenscalc_fitts_hick ~419 tokenscalc_print_spec ~388 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.allthepossibles%2Fdesigners?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.allthepossibles%2Fdesigners?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.allthepossibles%2Fdesigners.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.allthepossibles%2Fdesigners.svg :target: https://glimind.com/server/mcp-registry%2Fcom.allthepossibles%2Fdesigners?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b447224335698492…, first seen 2026-10-24, included at leaf 55533 of 74,582. Version history · verify what your client received.
Compare: most reliable accessibility servers · most reliable research servers · most reliable other servers · most reliable knowledge servers · most reliable code servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 17:58 UTC, the Allthepossibles Designers MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Allthepossibles Designers MCP server advertises 141 tools, including alt_text_quality, analyse_card_sort, approx_print_colour, audit_dark_patterns, audit_email_accessibility.
Point your MCP client at this streamable-http endpoint: https://designers.allthepossibles.com/mcp
Glimind scanned all 141 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.