Logic Analyzer Ai Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Logic Analyzer Ai Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
An MCP (Model Context Protocol) server for interfacing with Saleae Logic analyzers. This tool allows AI assistants (like Claude) to control hardware logic analyzers, capture signals, and export data for analysis.
This project uses uv for dependency management, but standard pip works too.
uv (Recommended) git clone https://github.com/wegitor/logic-analyzer-ai-mcp.git
cd logic-analyzer-ai-mcp uv venv
uv sync uv pip install -e .To run the server and see available tools:
# Activate virtual environment first
.venv\Scripts\activate
# Run the server with Logic 2 automation enabled
python -m src.logic_analyzer_mcp --logic2To use this with Claude Desktop, add the following to your config file:
%APPDATA%\Claude\claude_desktop_config.json~/Library/Application Support/Claude/claude_desktop_config.json{
"mcpServers": {
"saleae_logic": {
"command": "c:\\path\\to\\logic-analyzer-ai-mcp\\.venv\\Scripts\\python.exe",
"args": [
"c:\\path\\to\\logic-analyzer-ai-mcp\\src\\logic_analyzer_mcp.py",
"--logic2"
]
}
}
}Note: Replace `c:\\path\\to\\...` with the actual absolute path to your project folder.
Once connected, the AI assistant will have access to tools like:
logic2_reconnect: Connect to the running Saleae software.get_available_devices: List connected hardware or simulation devices.create_device_config: Set up channels and sample rates.capture_and_analyze_digital: One-shot capture + frequency/duty cycle analysis.capture_and_analyze_analog: One-shot capture + voltage statistics.start_capture / wait_capture / save_capture: Granular control over the capture workflow.start_capture_with_trigger: Wait for a digital event (e.g. Rising Edge) before capturing.add_protocol_analyzer: Add decoders like Serial, I2C, SPI to the capture.export_analyzer_data: Export decoded text data to CSV.To capture only when a specific event happens:
create_device_config). # Example: Wait for Rising Edge on Channel 0, then record 1 second
start_capture_with_trigger(
device_config_name="my_config",
trigger_channel_index=0,
trigger_type="RISING",
after_trigger_seconds=1.0
)To decode UART/Serial data and export the text:
add_protocol_analyzer(
name="Async Serial",
label="MySerial",
settings={
"Input Channel": 0,
"Bit Rate": 115200
}
) export_analyzer_data(
filepath="C:\\temp\\serial_data.csv",
analyzer_label="MySerial"
)digital_threshold_volts value (the tool handles this automatically now).~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.