Design Check

Scores whether a page reads as AI-generated and names the tells to fix.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
97%
Calidad de los nombres
100%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~509Tokens (definiciones de herramientas)
~432 BTamaño de respuesta típico
Impacto mínimo en la atención (0.40% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "designcheck": {
      "url": "https://designcheck.allthepossibles.com/mcp"
    }
  }
}

Puntos de conexión remotos

https://designcheck.allthepossibles.com/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (3)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢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.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "code": {
      "type": "string",
      "description": "The source file or diff to check"
    }
  },
  "required": [
    "code"
  ]
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada3 herramientas