Skip to main content
Glama
andy-qingcai

KingstVIS MCP Server

by andy-qingcai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to KingstVIS MCP Server

No user-submitted related servers found.

    Related Servers

    • logic-analyzer-ai-mcp

      wegitor
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables remote control and automation of Saleae logic analyzers for capture, export, and protocol decoding.
      10
      -

    • ATK-Logic-MCP

      hugelzhang
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to capture digital waveforms from an ALIENTEK USB logic analyzer, run 208 sigrok protocol decoders with stacked chains (like I2C→SSD1306 or UART→Modbus), and analyze or write .atkdl waveform archives offline without the device attached.
      1
      MIT

    • dwf-mcp-server

      KenosInc
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables control of Digilent WaveForms instruments (oscilloscope, AWG, logic analyzer) over USB, supporting devices like Analog Discovery 2/3 and Digital Discovery.
      3
      MIT

    • logic-mcp

      dengtaowei
      A
      license
      C
      quality
      C
      maintenance
      Enables MCP clients like Cursor to control logic analyzers, open capture files, decode buses such as Intel 8080, and reconstruct display framebuffers like ST7789.
      19
      MIT

    • oscilloscope-mcp

      lxkang00
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables remote control of Siglent oscilloscopes via SCPI over TCP/IP, allowing natural language commands for configuration, measurements, and waveform data retrieval.
      -
    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

    A3.7/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools target a distinct resource or action, with clear get/set/list/export/parse/measure families. A few pairs could initially be confused, such as start versus capture and raw_command versus the structured tools, but the descriptions clarify their roles.

    Naming Consistency4/5

    Tool names mostly follow a predictable verb_noun pattern: get_*, set_*, list_*, export_*, add_*, remove_*. A few bare verbs like connect, disconnect, start, stop, capture, and the noun-only raw_command are minor deviations, but the overall style remains consistent and readable.

    Tool Count3/5

    26 tools is on the heavy side for an MCP server, and the set covers many distinct concerns: connection, configuration, acquisition, export, analyzers, and offline analysis. The count is borderline but each tool does appear to serve a specific purpose within that broad scope.

    Completeness4/5

    The tool surface covers the full acquisition lifecycle, analyzer management, export, and offline parsing/measurement. Minor gaps exist, such as no getters for sample depth, sample time, threshold voltage, or trigger configuration, though raw_command and get_actual_* tools provide partial workarounds.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources