uni-t-uts-mcp
Related Servers
Alternatives to uni-t-uts-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for controlling Hantek DSO2D15 and other DSO2000-family oscilloscopes via USB and SCPI, enabling waveform acquisition, measurements, and screen captures.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables control and data capture from compatible oscilloscopes over SCPI/VISA, including channel and trigger configuration, measurements, waveform retrieval, screenshots, and raw SCPI commands through MCP tools.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to control a tinySA spectrum analyzer over USB, discovering the device, capturing or scanning spectra, configuring RBW/attenuation/units, and finding peaks, with CSV and JSON exports. It runs headless with automatic port detection and no GUI or network listener.1011MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for controlling SIGLENT oscilloscopes and signal generators via USBTMC, enabling waveform generation, scope configuration, measurement, and evidence reporting for electronics competitions.1-
- AlicenseNot gradedqualityDmaintenanceMCP server for reading and controlling an OWON SPE6103 programmable DC power supply over USB serial, with safety checks and verified SCPI commands.MIT
- FlicenseNot gradedqualityBmaintenanceEnables unified discovery, query, and control of laboratory instruments (power supplies, oscilloscopes, signal generators, multimeters) via VISA/SCPI, with device-specific libraries and an MCP server exposing 19 tools for natural language interaction.-
TDQS
Scored across 85 tools
Most tools have a clearly distinct resource/action, and module-specific prefixes plus explicit 'EMI/AD module must be active' notes separate the SA, EMI and AD variants. However the parallel marker, limit-line and peak-criteria families (get_marker vs get_emi_marker vs get_ad_marker; set_marker vs ad_marker) create real misselection risk in such a large set.
All names are snake_case, but conventions are mixed: many get_/set_ verb_noun pairs coexist with action-first names (measure, connect, identify, screenshot), odd forms (marker_to_instrument, emi_signal_list), and ad_marker acting as a setter while get_ad_marker is the reader. The set is readable overall, but not predictably patterned.
85 tools is far above the practical 3-15 range and makes the surface hard for an agent to navigate. Although the server covers three instrument modules and many settings, the count is excessive for an agent-facing toolset.
Coverage is very broad across SA, EMI and AD: settings get/set pairs, measurement lifecycle, markers, limit lines, traces, sweeps, discovery/connect, and raw SCPI escape hatches. Gaps exist where the instrument exposes no read-back (trace math, EMI signal list, limit-line pass/fail) and some AD display state lacks a getter, but core workflows are covered.