Skip to main content
Glama
kitour

RIGOL MHO98 MCP

by kitour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to RIGOL MHO98 MCP

No user-submitted related servers found.

    Related Servers

    • rigol-mcp

      gloveboxes
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to discover tools, configure a Rigol oscilloscope over LAN, take measurements, and retrieve waveform captures via a containerized stdio server.
      21
      MIT

    • rigol-dho-mcp

      mattjax16
      A
      license
      A
      quality
      B
      maintenance
      MCP server for controlling and reading Rigol DHO800/DHO900 oscilloscopes over LAN via SCPI commands.
      11
      2
      MIT

    • rigol-oscilloscope-mcp

      zinntikumugai
      A
      license
      A
      quality
      A
      maintenance
      Enables LLMs to control RIGOL oscilloscopes over SCPI via LAN or USB, including configuring channels/timebase/trigger, taking measurements, capturing waveforms and screenshots, decoding serial protocols, running FFT analysis, and controlling the built-in AFG.
      38
      MIT

    • ScopeMCP

      Kletternaut
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects AI assistants to the Owon DS1102 oscilloscope, enabling waveform capture, measurement retrieval, and remote control of scope settings.
      GPL 3.0

    • instrument_mcp

      Xingwen37
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI to control RIGOL DHO/HDO oscilloscopes and SIGLENT SDG1000X signal generators via SCPI commands through a local stdio MCP server.
      1
      -

    • SkippyMCP

      krystalmonolith
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for controlling Rigol oscilloscopes from an AI assistant. It translates MCP tool calls into SCPI commands over PyVISA.
      1
      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.2/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct function: acquisition control (run/stop/single/autoscale), configuration (set_channel/set_timebase/set_trigger), measurement (measure/measure_between), data retrieval (get_waveform/get_scope_state/get_cursor_values), and utilities (idn/check_error/screenshot). Even similar tools like run/stop/single are clearly differentiated by their descriptions.

    Naming Consistency4/5

    All tools use snake_case with clear verb prefixes (get_, set_, check_, measure_) and action verbs (run, stop, single, autoscale). Minor inconsistency: some tools are single verbs without object nouns, but the pattern is predictable and readable.

    Tool Count4/5

    16 tools is slightly above the ideal range but justified for a complex oscilloscope with acquisition, configuration, measurement, and diagnostic capabilities. Each tool has a defined role and none are redundant.

    Completeness4/5

    The surface covers all core oscilloscope workflows: acquisition, channel/timebase/trigger configuration, single and between-channel measurements, waveform capture, cursor operations, and diagnostics. Minor gaps like non-edge trigger types (e.g., pulse, video) exist but are not essential for basic usage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources