GridProof
OfficialRelated Servers
Alternatives to GridProof
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to inspect a project's design tokens and component catalog, audit React/Tailwind files against seven static UI quality rules, score overall UI health, and apply auto-fixes that are re-audited and reverted on regression. It works both locally over filesystem access and remotely on raw TSX/JSX or CSS snippets passed directly as strings.-
- AlicenseAqualityCmaintenanceEnables AI agents to audit and fix CSS for generic AI-built design patterns, covering fonts, palettes, contrast, and type scales.646 npmMIT
- AlicenseAqualityCmaintenanceProvides deterministic UI/UX intelligence and systems performance auditing tools for AI coding agents, enabling generation of accessible, well-designed React/Tailwind interfaces and elimination of backend anti-patterns like N+1 queries and sequential waterfalls.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to deterministically audit markup and stylesheets for WCAG contrast failures, accessibility errors and design-token sprawl, and to compute contrast ratios and inventory hardcoded colors, sizes, radii and spacing before shipping UI code. Works across any web stack with Claude Code, Claude Desktop, Codex and Antigravity, and can also run as a CI check that exits non-zero on errors.64 npmMIT
- AlicenseBqualityBmaintenanceEnables AI coding agents to absorb UI references into perceptual design tokens, semantic responsive layout skeletons, motion physics parameters, and zero-dependency multi-framework components, while auditing WCAG contrast, touch targets, reduced-motion guardrails, and layout stability.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to audit rendered web pages for design and UI defects by measuring geometry, styles, contrast and motion in a local browser and judging them against evidence-tiered rules. Findings come back as short, fixable items expressed in the project's own design tokens, while only sanitized numeric measurements leave the machine.Apache 2.0
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: gp_audit runs a full audit, gp_check_element re-checks a specific subtree, gp_get_config retrieves configuration, and gp_report writes an HTML report. No two tools overlap in purpose, so an agent can confidently choose the right one.
All tools follow a consistent gp_ verb_noun pattern (gp_audit, gp_check_element, gp_get_config, gp_report), with the verb indicating the action and the noun indicating the target. This uniformity makes the toolset predictable and easy to navigate.
Four tools is an ideal size for a focused auditing server. Each tool addresses a distinct need without redundancy or bloat, and the count is well within the recommended 3–15 range.
The toolset covers the full workflow: run an audit, re-check a single element after fixes, retrieve effective configuration, and generate a standalone HTML report. There are no obvious dead ends, and configuration management is appropriately delegated to the config file.