ToolBB-0099

mcp-hardware-tools: Claude judges its own scope captures and fixes the setup

mcp-hardware-tools connects Claude to a Rigol DS1054Z oscilloscope and decodes SPI, I2C and UART from raw waveforms. Each capture comes back with clipping and trigger-status flags, and the agent adjusts the setup and captures again. The author reports bench tests against known signals from a JDS6600 generator and a Pico 2, and no use yet on an unknown fault.

Open original source github.com · Louis Pender

Claimed
Why this evidence label?

Author describes hardware-in-the-loop tests against a real DS1054Z, JDS6600 and Pico 2; no captures or CI logs shown.

How we check entries
Preview image for mcp-hardware-tools: Claude judges its own scope captures and fixes the setup
The source's own preview image, from github.com.

Briefing

In a development test the harness emits a known pattern, such as 0xA5 over SPI at 1 MHz, and the scope tooling has to capture, auto-scale, trigger and decode it back to 0xA5. A Raspberry Pi Pico 2 emulates digital devices with its PIO state machines, as initiator or target. The JDS6600 supplies analog stimulus, since the Pico 2 has no DAC. The decoders are pure functions over sample arrays and are unit-tested without hardware.

The author calls the harness development scaffolding, not part of the tool. The project grew from two bench jobs: electrochemical impedance spectroscopy and bringing up a field-oriented motor controller. The README's getting-started section is still a placeholder, and a wideband noise source for system identification is listed as future work.

“What it has not done yet is debug something it did not already know the answer to”

Louis Pender, in the source on github.com

From the GitHub API

Repository facts

Repository facts for lpender3672/mcp-hardware-tools, from the GitHub API
Repositorylpender3672/mcp-hardware-tools
Stars0
LicenseApache-2.0 Permissive
LanguagePython
Last push7 Oct 2026 22 d ago

Tags

Agent

Report a problem with this entry