Skip to main content
Glama
wilsonvargas

DriftCheck

by wilsonvargas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to DriftCheck

No user-submitted related servers found.

    Related Servers

    • lazy-mobile-mcp

      leaf76
      A
      license
      Not graded
      quality
      D
      maintenance
      Local MCP server for Android and iOS mobile automation and performance telemetry, enabling device control (screenshot, tap, swipe, input, app launch) and metric collection (CPU, memory, launch time) via ADB, simctl, and WebDriverAgent with SQLite session history.
      3 npm
      1
      MIT

    • Soma Nexus MCP

      pablostefan
      F
      license
      B
      quality
      D
      maintenance
      MCP server that fetches Figma data (file trees, nodes, images, components, styles, variables) and serves as a foundation for Flutter code generation.
      13
      -

    • ios-sim-mcp

      artmamedov
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for iOS Simulator automation. Enables AI assistants to visually interact with iOS apps running in the simulator.
      97 npm
      1
      MIT

    • asdesigned

      Maher-Reven
      A
      license
      Not graded
      quality
      B
      maintenance
      Diff rendered UI components against their Figma sources to identify visual drift, with an MCP server for coding agents to verify design compliance.
      24 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a clear primary purpose, but capture_screen and compare_screen could be mistaken at a glance since compare_screen internally captures and analyzes the screen. get_design_specs and import_design also both deal with Figma source data, though their descriptions clearly distinguish API vs offline export use.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern: list_devices, compare_screen, capture_screen, get_design_specs, import_design. No mixed conventions or vague standalone verbs.

    Tool Count5/5

    Five tools is well-scoped for a visual design comparison server. Each tool covers a distinct step in the workflow: device discovery, screenshot capture, Figma spec retrieval, offline design import, and comparison.

    Completeness4/5

    The core workflow is covered: discover devices, get design specs or import design data, capture the current UI, and compare it against Figma with reports. Minor gaps exist around explicit device selection or app navigation/state control, but agents can likely work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources