Skip to main content
Glama
donaldrichard19-LVD

ui-component-judgment-mcp

Related Servers

Alternatives to ui-component-judgment-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Provides coding agents live access to shadcn-style component registries, enabling them to search, compare, and fetch real component source code for UI composition.
      5
      61 npm
      5
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Design review for UI code, inside your coding agent. Reviews React, Vue, Svelte, CSS and SwiftUI against 313 rules and returns scored findings with file:line fixes your agent can apply and verify.
      -
    • A
      license
      B
      quality
      D
      maintenance
      Provides AI assistants with tools to grade, generate, and validate UI components against the components.build specification. Supports searching documentation, checking compliance, and generating framework-agnostic accessible components.
      11
      6 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      STOP UI SLOP. Gives coding agents searchable evidence from 800,000+ real web and iOS screens, design contracts, and a hard UI finish gate.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents and CI to verify rendered web UIs against design token usage, layout constraints, and accessibility rules, returning concise pass/fail verdicts with actionable findings.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to score live URLs against a 40-check design contract, validate DTCG tokens and Lottie animations, audit accessibility, and retrieve design-system contracts, catalogs, and review rubrics.
      20 npm
      MIT

    TDQS

    A4.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined and unambiguous.

    Naming Consistency5/5

    The tool name 'recommend_component' follows a clear verb_noun pattern, which is consistent with common naming conventions. No other tools exist to introduce inconsistency.

    Tool Count3/5

    A single tool is on the thin side for most servers, but it serves a specific, well-defined purpose. It is not trivial and may be sufficient for the intended scope, though additional related tools could add value.

    Completeness5/5

    The tool fully covers its stated purpose: making a judgment between using existing components or building custom. It provides a structured verdict without missing essential aspects like referencing Mobbin or shadcn/ui. No obvious gaps within the defined domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues