Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

EmbeddedCI BenchPod

PYPI · EMBEDDEDCI-MCP

Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.

Available components

−16 this week 77 Trust /100

Last scanned (14 hours ago)

Scores higher than 71% of PyPI servers

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 33 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to embeddedci-com/embeddedci-python). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 21643 tokens (~186/item across 116 items; 111 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability check failed: the tool surface changed between 2.13.2 and 4.0.2: 12 tool removals, 6 breaking changes, 47 additions. See how to fix → Fail
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 81% of tool parameters carry a description.Partial
  • Structured output schemas are declared (99% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 113 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Package version: 4.0.0 → 4.0.2 functional
    • Package version: 4.0.0 → 4.0.1 functional
  • 20 Nov 26 −1
    • Malware scan: unverified → pass ▲ security
    • Package version: 3.0.5 → 4.0.0 functional
  • 19 Nov 26 0
    • Package version: 3.0.2 → 3.0.5 functional
    • Package version: 3.0.2 → 3.0.4 functional
    • Package version: 3.0.2 → 3.0.3 functional
  • 18 Nov 26 0
    • Package version: 3.0.1 → 3.0.2 functional
  • 17 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Schema quality: 17468 → 19503 ▼ functional
    • Schema quality: 17468 → 19379 ▼ functional
    • Package version: 2.13.20 → 3.0.1 functional
    • Package version: 2.13.20 → 3.0.0 functional
  • 16 Nov 26 0
    • Malware scan: pass → unverified ▼ security
    • Package version: 2.13.18 → 2.13.20 functional
    • Package version: 2.13.18 → 2.13.19 functional
  • 15 Nov 26 0
    • Package version: 2.13.17 → 2.13.18 functional
  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Package version: 2.13.13 → 2.13.17 functional
    • Package version: 2.13.13 → 2.13.16 functional
    • Package version: 2.13.13 → 2.13.15 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/embeddedci-mcp@4.0.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo embeddedci-com/embeddedci-python
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/embeddedci-com/embeddedci-python/.github/workflows/publish.yml@refs/tags/embeddedci-mcp-v4.0.2
Rekor log index 4031203623
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:87c97a855f6eb97955b2198ce117bfdaa23b2b3d4cacabac84e3648905d7e7f9

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 33 packages
Packages resolved 33
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 111 exposed · ~18,376 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
adc_range ~314

Read or switch the ADC input range (analog module v3r4 and later, firmware 3.9.5+). normal is the ÷12 divider: ±32.8 V, about 1 mV per count. low is ÷2: ±5.46 V, about 167 µV per count, 6x the resolution for signals up to ±5 V. The low range's input is 1.82 MΩ: tell the user to use 1x leads, not a 10x scope probe. It applies to ext, cal1 and current_in (not cal2), and stays until changed, analog_path off or cal2, or a pod restart. capture_adc and adc_read scale with the range in use. A board without the low range refuses low. Use low for small signals; switch back to normal when a reading or capture reports overrange.

NameTypeReqDescription
range––ADC input range: normal (±32.8 V, ~1 mV/count) or low (±5.46 V, ~167 µV/count, 1.82 MΩ input: 1x leads only; analog module v3r4+). Omit to keep the range the pod is in.
testboolean–Run the self-test instead: the 5 V output drives the cal1 loopback at 1 V and 3.5 V and both ranges read it. Nothing may be connected to the 5 V output.
NameTypeReqDescription
fullscalenumberyesFull scale of the range in use, volts (±).
low_fullscale––Full scale of the low range, volts (±); null without it.
normal_fullscalenumberyesFull scale of the normal range, volts (±).
rangestringyesThe ADC input range in use: normal (±32.8 V) or low (±5.46 V).
supportedbooleanyesThe board has the low range (analog module v3r4 and later).
test––The self-test's result (test=true only).

No examples provided.

adc_read ~214

One calibrated voltage: ext = front SMA (true volts), cal1/cal2 = DAC loopbacks, current_in = 4-20 mA input (J8). current_in also returns current, the loop current in amps. range low reads small signals (up to ±5.46 V) at 6x the resolution on analog module v3r4+; overrange says the input clipped. From analog module v3r5 current_in reads in the low range unless range is given (the next other route gives normal back). Refused while the input is still moving (e.g. a DAC output left running).

NameTypeReqDescription
range––ADC input range: normal (±32.8 V, ~1 mV/count) or low (±5.46 V, ~167 µV/count, 1.82 MΩ input: 1x leads only; analog module v3r4+). Omit to keep the range the pod is in.
sourcestring––
NameTypeReqDescription
countintegeryes–
current––Loop current in amps on the 4-20 mA input (current_in only): 0.004 to 0.020 for a live loop.
fullscale––That range's full scale, volts (±).
offset––The pod's own calibration offset in volts, already taken out of voltage (current_in only).
overrangeboolean–A sample sat on an ADC rail: the input is past fullscale and voltage is only a bound. Read again in the normal range.
range––The ADC input range the reading was taken in: normal or low (firmware 3.9.5+).
sense_ohms––The resistance current was computed with, ohms (current_in only, firmware 3.10.13+): 249 up to analog module v3r4, about 100 from v3r5 (100 ohm behind a 30 mA limiter, so a loop reads at most 28.5 to…
sourcestringyes–
spanintegeryes–
voltagenumberyes–

No examples provided.

analog_path ~212

Set every analog mux and relay for a named path in one step. dac_3v3/dac_5v/dac_12v route the DAC to an output; adc_ext connects the ADC to the front SMA; cal1/cal2 loop the 5 V/12 V DAC output back into the ADC; current_in reads the 4-20 mA input (J8); current_out switches the DAC voltage outputs off for the 4-20 mA output (J9); off parks everything. range also sets the ADC input range (see adc_range); off and cal2 put it back to normal.

NameTypeReqDescription
pathstringyes–
range––ADC input range: normal (±32.8 V, ~1 mV/count) or low (±5.46 V, ~167 µV/count, 1.82 MΩ input: 1x leads only; analog module v3r4+). Omit to keep the range the pod is in.
NameTypeReqDescription
pathstringyes–
range––The ADC input range in use afterwards: normal or low (firmware 3.9.5+; null on older firmware).

No examples provided.

calibrate ~257

Calibrate the pod's ADC offset on its 4-20 mA input (current_in, terminal J8) and store it on the pod. Nothing may be connected to J8: ask the user to disconnect it and confirm before calling. The pod reads its open input (0 V) and keeps that offset in flash. Every later adc_read on current_in has it taken out, and on firmware 3.9.3+ every other ADC source and capture too (they share the front end). Once per pod is enough: it survives reboots and firmware updates. The pod refuses, and keeps what it had, when something is driving J8 (more than 150 mV; 50 mV before 3.9.3). clear=true removes the stored calibration (all of it, or clear_part only).

NameTypeReqDescription
clearboolean–True removes the stored calibration instead of measuring one.
clear_part––With clear=true, remove only this part: offset, dac (the DMM lines) or adc (the ADC gains). Firmware 3.9.4+.
sourcestring–What to calibrate. Only current_in, the 4-20 mA input.
NameTypeReqDescription
anumberyesThe fit the pod now uses: volts at count 0 (volts = a + b * count).
adc_comp––The ADC input's recorded frequency response: hf_dc_gain (high-frequency gain against DC, 1.0 is flat) and c_top_pf. Reference only, no reading is scaled with it. null: not measured.
adc_gain_ppmobject–ADC gain correction per source (cal1, cal2, ext) in ppm; null = the built-in gain.
adc_low_gain_ppm––The ADC low range's gain correction in ppm (analog module v3r4+); null = the nominal divider ratio.
bnumberyesVolts per count.
calibratedbooleanyesTrue when the pod has its own calibration stored.
count––Mean raw count of the calibration measurement (only right after calibrating).
dacobject–This pod's DMM line per DAC output (3v3, 5v, 12v); null = the built-in line. Empty before firmware 3.9.4.
dmmboolean–True when any DMM-guided part is stored.
measured––After calibrate_adc_gain: v1, v2 (what the DAC put out), r1, r2 (what the ADC read before the gain) and residual (offset left after it), in volts.
offsetnumberyesWhat the input read with nothing connected, in volts. Taken out of every reading.
samples––Samples averaged.
sourcestringyes–
span––Its peak-to-peak spread in counts.
zero_count––The raw zero the offset is derived from: the mean ADC count with J8 open, unwrapped (firmware 3.9.4+).

No examples provided.

calibrate_adc_gain ~225

Measure and store an ADC source's gain against a DMM-calibrated DAC output (firmware 3.9.4+). Needs the ADC offset (calibrate) and the driving output's DMM line (calibrate_dac on 5v for cal1, 12v for cal2 and ext). For ext, ask the user to connect the SMA cable first. The pod drives two set points itself and switches the outputs off afterwards; measured says what it saw. Nothing to read on a DMM.

NameTypeReqDescription
rangestring–low measures the ADC low range's gain instead (analog module v3r4+, firmware 3.9.5+): source must be cal1, and the one gain serves every source in the low range.
sourcestringyescal1 (and current_in) through the 5 V output, cal2 through the ±12 V output, ext (the front SMA, captures and the control loop) through an SMA cable from the ±12 V output to the ADC input.
NameTypeReqDescription
anumberyesThe fit the pod now uses: volts at count 0 (volts = a + b * count).
adc_comp––The ADC input's recorded frequency response: hf_dc_gain (high-frequency gain against DC, 1.0 is flat) and c_top_pf. Reference only, no reading is scaled with it. null: not measured.
adc_gain_ppmobject–ADC gain correction per source (cal1, cal2, ext) in ppm; null = the built-in gain.
adc_low_gain_ppm––The ADC low range's gain correction in ppm (analog module v3r4+); null = the nominal divider ratio.
bnumberyesVolts per count.
calibratedbooleanyesTrue when the pod has its own calibration stored.
count––Mean raw count of the calibration measurement (only right after calibrating).
dacobject–This pod's DMM line per DAC output (3v3, 5v, 12v); null = the built-in line. Empty before firmware 3.9.4.
dmmboolean–True when any DMM-guided part is stored.
measured––After calibrate_adc_gain: v1, v2 (what the DAC put out), r1, r2 (what the ADC read before the gain) and residual (offset left after it), in volts.
offsetnumberyesWhat the input read with nothing connected, in volts. Taken out of every reading.
samples––Samples averaged.
sourcestringyes–
span––Its peak-to-peak spread in counts.
zero_count––The raw zero the offset is derived from: the mean ADC count with J8 open, unwrapped (firmware 3.9.4+).

No examples provided.

calibrate_dac ~333

Store this pod's own line for a DAC output from two DMM readings (firmware 3.9.4+, cap cal_dmm). The flow, with the user holding a bench DMM: ask them to disconnect the DUT from the output and put the DMM (DC volts) on that output's SMA. Drive each set point with dac_output(path, volts) and keep its code16 (3v3: 0.5 and 3.0 V, 5v: 1.0 and 4.0 V, 12v: -5 and +5 V), ask the user what the DMM reads, then call this with both points and switch the output off (dac_output path off). From then on dac_output, generate and the DAC output limits use this line. The pod refuses, and keeps what it had, when the codes are too close, a reading is far from what the output should give (DMM on the wrong SMA) or the gain is more than 2 % off.

NameTypeReqDescription
code1integeryesThe 16-bit code of the first set point: code16 from dac_output.
code2integeryesThe 16-bit code of the second set point.
pathstringyesThe DAC output: 3v3, 5v or 12v.
volts1numberyesWhat the DMM read at the first set point, in volts.
volts2numberyesWhat the DMM read at the second set point, in volts.
NameTypeReqDescription
anumberyesThe fit the pod now uses: volts at count 0 (volts = a + b * count).
adc_comp––The ADC input's recorded frequency response: hf_dc_gain (high-frequency gain against DC, 1.0 is flat) and c_top_pf. Reference only, no reading is scaled with it. null: not measured.
adc_gain_ppmobject–ADC gain correction per source (cal1, cal2, ext) in ppm; null = the built-in gain.
adc_low_gain_ppm––The ADC low range's gain correction in ppm (analog module v3r4+); null = the nominal divider ratio.
bnumberyesVolts per count.
calibratedbooleanyesTrue when the pod has its own calibration stored.
count––Mean raw count of the calibration measurement (only right after calibrating).
dacobject–This pod's DMM line per DAC output (3v3, 5v, 12v); null = the built-in line. Empty before firmware 3.9.4.
dmmboolean–True when any DMM-guided part is stored.
measured––After calibrate_adc_gain: v1, v2 (what the DAC put out), r1, r2 (what the ADC read before the gain) and residual (offset left after it), in volts.
offsetnumberyesWhat the input read with nothing connected, in volts. Taken out of every reading.
samples––Samples averaged.
sourcestringyes–
span––Its peak-to-peak spread in counts.
zero_count––The raw zero the offset is derived from: the mean ADC count with J8 open, unwrapped (firmware 3.9.4+).

No examples provided.

calibration ~96

The calibration the pod has stored: the ADC offset (measured on current_in, terminal J8) and the fit it uses, and on firmware 3.9.4+ the DMM-guided parts (dac: a line per DAC output, adc_gain_ppm: a gain per ADC source). calibrated=false means the pod has no ADC offset: analog readings can be off by up to about 50 mV.

Input schema present but exposes no named parameters.

NameTypeReqDescription
anumberyesThe fit the pod now uses: volts at count 0 (volts = a + b * count).
adc_comp––The ADC input's recorded frequency response: hf_dc_gain (high-frequency gain against DC, 1.0 is flat) and c_top_pf. Reference only, no reading is scaled with it. null: not measured.
adc_gain_ppmobject–ADC gain correction per source (cal1, cal2, ext) in ppm; null = the built-in gain.
adc_low_gain_ppm––The ADC low range's gain correction in ppm (analog module v3r4+); null = the nominal divider ratio.
bnumberyesVolts per count.
calibratedbooleanyesTrue when the pod has its own calibration stored.
count––Mean raw count of the calibration measurement (only right after calibrating).
dacobject–This pod's DMM line per DAC output (3v3, 5v, 12v); null = the built-in line. Empty before firmware 3.9.4.
dmmboolean–True when any DMM-guided part is stored.
measured––After calibrate_adc_gain: v1, v2 (what the DAC put out), r1, r2 (what the ADC read before the gain) and residual (offset left after it), in volts.
offsetnumberyesWhat the input read with nothing connected, in volts. Taken out of every reading.
samples––Samples averaged.
sourcestringyes–
span––Its peak-to-peak spread in counts.
zero_count––The raw zero the offset is derived from: the mean ADC count with J8 open, unwrapped (firmware 3.9.4+).

No examples provided.

can_close ~29

Clear responder rules, stop CAN and switch the 120 ohm termination off (safe when not open).

Input schema present but exposes no named parameters.

NameTypeReqDescription
bitrate–––
data_bitrate–––
fd–––
mode–––
openbooleanyes–
term–––

No examples provided.

can_open ~170

Bring up the pod's CAN interface (replacing any open CAN session): classic CAN, or CAN FD (up to 64-byte frames) with data_bitrate.

NameTypeReqDescription
bitrateinteger––
data_bitrate––CAN FD: the data-phase bit rate (bit/s). Omit for classic CAN. Above bitrate, frames switch to it after arbitration; equal to bitrate, FD frames without switching. Exact rates only, e.g. 1, 2, 4, 5 o…
modestring–normal = on a bus with other nodes; internal/external = loopback self-test; listen = silent.
termboolean–Engage the 120 ohm termination.
NameTypeReqDescription
bitrate–––
data_bitrate–––
fd–––
mode–––
openbooleanyes–
term–––

No examples provided.

can_read ~69

Read received CAN frames (id, data, timestamps in pod milliseconds).

NameTypeReqDescription
can_id–––
max_framesinteger––
timeout_snumber–With can_id: wait up to this long for it. Without: collect frames for this long (0 = what is buffered).
NameTypeReqDescription
framesarrayyes–
matched–––

No examples provided.

can_respond ~139

Make the pod firmware answer a CAN id instantly (ECU simulation), or clear all rules.

NameTypeReqDescription
clearboolean–Remove all responder rules instead of adding one.
match_extboolean––
match_id–––
reply_brs––CAN FD replies only: false keeps the data phase at the nominal bitrate.
reply_data––Reply bytes: up to 8 on classic CAN, 64 on CAN FD.
reply_extboolean––
reply_fd––CAN FD bus only: false replies with a classic frame. Default: FD on an FD bus.
reply_id–––
NameTypeReqDescription
clearedboolean––
rules–––

No examples provided.

can_status ~29

CAN link state: mode, bitrate, data_bitrate (CAN FD), error counters, bus-off.

Input schema present but exposes no named parameters.

NameTypeReqDescription
replyobject––

No examples provided.

can_write ~151

Queue one CAN frame (classic, or CAN FD on a bus opened with data_bitrate).

NameTypeReqDescription
brs––CAN FD frames only: false keeps the data phase at the nominal bitrate. Default: switch.
can_idintegeryes–
data––0-8 data bytes on classic CAN, up to 64 on CAN FD (padded with zeros to 12, 16, 20, 24, 32, 48 or 64).
extboolean–29-bit extended identifier.
fd––CAN FD bus only: false sends a classic frame. Default: FD frames on an FD bus.
rtrboolean––
NameTypeReqDescription
brs–––
dlc–––
fd–––
queuedboolean––

No examples provided.

capture_adc ~467

Capture the ADC and summarise it: calibrated stats, dominant frequency and a min/max envelope. source current_in captures the 4-20 mA input (J8): the stats are then the loop current in amps (unit "A"), and replay(from_last_capture=true, dac_path="current_out") plays it back as a current. Above 32768 samples the capture streams from PSRAM (multi-second captures work). With trigger_la the capture waits for that edge or level, so t = 0 is the trigger moment. The capture is kept for replay and save_capture_as_recording. range low captures small signals (up to ±5.46 V) at 6x the resolution (see adc_range); clipped_samples > 0 means it clipped. oversample suits measuring small or near-0 V signals at low rates; the result's oversample says how many conversions each sample averages, and it fails if they do not fit in the pod's memory.

NameTypeReqDescription
oversampleboolean–Convert at 400 kS/s and average down to sample_rate_hz: lower noise and a smaller step at 0 V, for short captures (about 5 s at most).
pointsinteger–Points in the returned min/max envelope.
range––ADC input range: normal (±32.8 V, ~1 mV/count) or low (±5.46 V, ~167 µV/count, 1.82 MΩ input: 1x leads only; analog module v3r4+). Omit to keep the range the pod is in.
sample_rate_hz––Sample rate in Hz; omit for the device maximum.
samplesinteger––
source––Route this ADC source first; omit to keep routing.
trigger_edgestring–What starts the capture on trigger_la.
trigger_la––Wait for an edge or level on this LA channel (a number, or a wiring-profile name) before sampling, so t = 0 is that moment. Omit for a free-running capture. Needs the capture_trigger capability.
trigger_timeout_snumber–Seconds to wait for the trigger before the capture is abandoned with a TriggerTimeout.
NameTypeReqDescription
clipped_samplesinteger–Samples on an ADC rail: the input went past the range's full scale. Capture again in the normal range.
dominant_frequency_hz–––
durationnumberyes–
envelope_maxarrayyes–
envelope_minarrayyes–
envelope_stepnumberyesSeconds covered by each envelope point.
maxnumberyes–
meannumberyes–
minnumberyes–
oversampleinteger–ADC conversions averaged into each sample; 1 for a plain capture.
peak_to_peaknumberyes–
range––The ADC input range the capture was scaled for: normal or low (firmware 3.9.5+).
rmsnumberyes–
rms_acnumberyes–
sample_rate_hznumberyes–
samplesintegeryes–
source–––
trigger––The trigger that started the capture, e.g. 'LA9 rising'; null for a free-running capture. t = 0 is the trigger moment.
unitstring–Unit of mean, min, max, peak_to_peak, rms, rms_ac and the envelope: volts, or amps for a capture of the 4-20 mA input (source current_in): 0.004 to 0.020 for a live loop.

No examples provided.

capture_correlated ~292

ADC and LA captured from one hardware trigger, so their timebases align. Both are kept. With trigger_la both streams start on that edge or level. There is one ADC: the analog half is the SMA voltage or, with source current_in, the loop current on J8 (unit "A"), never both.

NameTypeReqDescription
adc_sample_rate_hz––Sample rate in Hz; omit for the device maximum.
adc_samplesinteger––
la_sample_rate_hz––Sample rate in Hz; omit for the device maximum.
la_samplesinteger––
pointsinteger–Points in the returned min/max envelope.
source––Route this ADC source first for the analog half; omit to keep routing. current_in captures the 4-20 mA input (J8) and the analog stats are then amps.
stop_dac_after_s––Seconds into the capture to cut a running DAC.
trigger_edgestring–What starts both streams on trigger_la.
trigger_la––Wait for an edge or level on this LA channel (a number, or a wiring-profile name) before sampling, so t = 0 is that moment. Omit for a free-running capture. Needs the capture_trigger capability.
trigger_timeout_snumber–Seconds to wait for the trigger before the capture is abandoned with a TriggerTimeout.
NameTypeReqDescription
adc–yes–
la–yes–

No examples provided.

capture_la ~372

Capture all 14 LA channels and summarise each: levels, edge count, first edge, estimated frequency. With trigger_la the capture starts on that edge or level instead of immediately, so a short event can be caught at a high sample rate. The capture is kept for decode_la and la_timing. sample_rate_hz goes up to 12 MS/s, or 48 MS/s on gateware v50+ (48, 24 or 16 MS/s); above 12 MS/s a signal changing over ~6 million times per second for long stops early (truncated); retry at 12 MS/s.

NameTypeReqDescription
sample_rate_hz––Sample rate in Hz; omit for the device maximum.
samplesinteger––
send––Run one transaction right after the capture arms (gateware v55+): i2c (the i2c_open session, else one from the wiring), spi (SPI pins from the wiring) or gpio (a GPIO output). Without trigger_la it t…
stop_dac_after_s––Seconds into the capture to cut a running DAC output (see the DUT react).
trigger_edgestring–What starts the capture on trigger_la.
trigger_la––Wait for an edge or level on this LA channel (a number, or a wiring-profile name) before sampling, so t = 0 is that moment. Omit for a free-running capture. Needs the capture_trigger capability.
trigger_pre_samplesinteger–With trigger_la: also return up to this many samples from before the trigger (gateware v50+).
trigger_timeout_snumber–Seconds to wait for the trigger before the capture is abandoned with a TriggerTimeout.
NameTypeReqDescription
channelsarrayyes–
durationnumberyes–
pre_samplesinteger–Samples before the trigger (trigger_pre_samples): the trigger is at this sample index.
sample_rate_hznumberyes–
samplesintegeryes–
send––What the capture's send did.
trigger––The trigger that started the capture, e.g. 'LA9 rising'; null for a free-running capture. t = 0 is the trigger moment.
truncated––Above 12 MS/s only: why the capture stopped early ('busy': the signals changed too often, 'memory'), so it holds fewer samples than asked; null when complete.

No examples provided.

capture_uart ~497

Record the DUT's UART output for a fixed window (or until until_regex matches). The channels, baud, parity and stop bits come from the wiring profile when omitted (8N1 unless the profile says otherwise). half_duplex runs it on one wire, and entry runs a pod-timed boot-mode entry first (reset with TX low, release, first bytes). de: the pod switches an RS-485 transceiver's DE on that LA channel while it sends.

NameTypeReqDescription
baud––UART baud rate; omit for the wiring profile's uart_baud.
de––LA channel (or wiring name) wired to an RS-485 transceiver's DE + /RE. The pod drives it high while it sends and low otherwise, so the transceiver listens whenever the pod is not sending and a fast d…
de_active_lowboolean–Drive DE low while sending (an active-low enable).
duration_snumberyesCapture window in seconds.
entry––Run a boot-mode entry on the pod first: TX low, reset, release, then the first bytes, all timed on the pod. Needs gateware v57 and the pod's reset pin. Omit for a plain session.
half_duplexboolean–One-wire UART: rx alone carries both directions (tx defaults to rx). The pod only pulls the line low and its pull-up (LA1-LA6) or the board's holds it high; the pod does not read back its own bytes.…
parity––Parity bit after the 8 data bits; omit for the profile's uart_parity (none unless set). Anything but 8N1 needs firmware 3.10.8+ (gateware v56).
rx––LA channel (or wiring name) wired to the DUT's TX; omit for the profile's uart_rx.
stop_bits––Stop bits after the data (and parity) bits; omit for the profile's uart_stop_bits (1 unless set).
tx––LA channel (or wiring name) wired to the DUT's RX; omit for the profile's uart_tx.
until_regex––Python regular expression; stop as soon as it matches.
NameTypeReqDescription
bytesintegeryes–
matchedbooleanyes–
textstringyes–
truncatedbooleanyestext keeps the start and the end when output is long.

No examples provided.

cloud_list_devices ~90

The BenchPods registered to your embeddedci.com organisation, and whether each is online. Drive one with connect(connection) using the returned `connection` ('embeddedci:<name>'). Needs no pod connection. Authenticates with BENCHPOD_API_KEY, else the session saved by `benchpod login` (~/.config/benchpod-cli/token.json), refreshing it when it has expired.

Input schema present but exposes no named parameters.

NameTypeReqDescription
authstringyesThe credential used: BENCHPOD_API_KEY, or the `benchpod login` session.
devicesarrayyes–

No examples provided.

cloud_run_compare ~120

What changed between an earlier run (a) and this one (b): newly failing and fixed cases, measurements that moved or broke a limit, slower tests and pod calls, and the inputs that differ (pod firmware, wiring, DUT firmware), so the likely cause sits next to the change.

NameTypeReqDescription
compare_withstring–'previous' (the newest earlier valid run of the same suite and DUT), a run id, or 'baseline:<branch>' (the newest valid run on that branch).
run_idstringyes–
NameTypeReqDescription
authstringyes–
diffobject–a (the earlier run), b (this one), comparable, reasons, flags, inputs_changed, cases (newly_failing, fixed, still_failing, new, removed, newly_skipped), measurements, slower, calls_slower, a_run (the…
foundbooleanyesFalse when there is no earlier run to compare with.
message–––

No examples provided.

cloud_run_get ~97

One test run: outcome, counts, health, the pod and tests it ran with, the failed cases with the first line of their message, and the measurements outside their limits. cloud_run_trace reads a failed case's pod calls; cloud_run_compare shows what changed since an earlier run.

NameTypeReqDescription
fullboolean–Also return the whole run.json (every case, inputs, calls).
run_idstringyes–
NameTypeReqDescription
authstringyes–
filesarray–The uploaded files (name, size_bytes, expired): junit.xml, the traces of failed cases.
run––The full run.json, with full=true.
summaryobjectyesid, url, suite, dut, outcome, counts, valid, health_reasons, pod, tests, build_id, failed_cases (id, outcome, the message's first line, whether a trace was uploaded) and measurements_out_of_limits.

No examples provided.

cloud_run_trace ~110

Every call a test case made to the pod (what it sent, how long it took, what the pod answered), from the trace uploaded with the run. Only failed and error cases have one.

NameTypeReqDescription
case_idstringyesThe case id (pytest node id), or a unique end of it ('test_ack').
errors_onlyboolean–Only the calls that failed.
limitinteger–How many lines, from the start.
run_idstringyes–
NameTypeReqDescription
authstringyes–
casestringyes–
errorsintegeryesCalls that failed (ok false).
linesarrayyesOne object per pod call: t (s since the run started), op, cmd, req, ms, ok, resp or error; long req/resp are shortened.
shownintegeryes–
totalintegeryes–
tracestringyesThe trace file's name in the run.
truncatedbooleanyesMore lines exist than `limit` returned.

No examples provided.

cloud_runs_list ~155

Test runs uploaded to embeddedci.com (benchpod ci, pytest --embeddedci-upload, build_report), newest first, with their outcome and counts. Needs no pod connection; authenticates like cloud_list_devices.

NameTypeReqDescription
before––The next_before of the previous page.
build––Only the runs linked to this build id.
dut––Only this board under test ('none' for pod-only suites).
limitinteger–How many runs, newest first.
pod––Only the runs on this pod (name or id).
ref––Only the runs of this git branch or ref of the tests.
suite––Only this suite (the run's key.suite).
NameTypeReqDescription
authstringyes–
next_before––More runs exist: pass this as `before` for the next page.
org_pods––How many pods the organization has.
runsarrayyesNewest first: id, url, suite, dut, outcome, valid, counts, started, duration_ms, build_id, device_name, tests_ref, tests_sha, firmware, github_run_url.

No examples provided.

command ~49

Escape hatch for firmware commands no tool covers. Prefer the dedicated tools.

NameTypeReqDescription
requestobjectyesA firmware JSON command with a "cmd" key, e.g. {"cmd": "usb_cc"}.
NameTypeReqDescription
reply–––

No examples provided.

connect ~330

Open a BenchPod connection (closing any previous one and its sessions) and report status. Over the cloud the device is shared: this takes an exclusive lease, released by `disconnect` or after the server's idle timeout (the next tool call then reconnects).

NameTypeReqDescription
connection––host[:port] (TCP: TLS on 8443 by default, with the pod's certificate pinned on first use; plaintext only with an explicit :8080 or on the USB network adapter), a serial device path (the USB console,…
la_voltage––Select the LA I/O-bank voltage right after connecting (the DUT's I/O voltage; 5.0 needs the digital board v3r4).
lease_wait_snumber–Seconds to wait when someone else holds the pod's lease (the cloud device's, or the pod's own on the LAN and USB network).
wiring_profile––A wiring profile stored on the pod to use (the `wiring` tool lists them); omit for the pod's default profile.
NameTypeReqDescription
capabilities–––
connectedbooleanyes–
connection–––
eth_mac––The pod's Ethernet MAC (aa:bb:cc:dd:ee:ff), for a network that hands out addresses only to registered devices; null when not known (firmware 3.10.7 and older over the LAN).
firmwareobject–The pod's raw status report.
kind––tcp, serial (USB console), usb_net ('usb' reached the pod's USB network adapter), discover or embeddedci (cloud).
la_voltage––Selected LA bank voltage; null = not set.
leasedboolean–This session holds an exclusive lease: the server's on a cloud device, or the pod's own lease on the LAN or USB network.
local_lease––The pod's own lease (held, holder, purpose, left_s, mine), on firmware with the lease feature; null otherwise.
session–––
warningsarray––
wifi_mac––The MAC the pod uses on Wi-Fi; null on a pod without Wi-Fi, or until the pod scanned for Wi-Fi or joined a network. Over the cloud both come from embeddedci.com's record of the pod.
wiring_source––Where this connection's wiring profile came from: server (stored on embeddedci.com, as the web UI's Wiring tab shows it), file (BENCHPOD_WIRING), dict (set_wiring) or defaults.

No examples provided.

control_loop ~268

Run a tabulated transfer function in the FPGA: each tick out = curve[input], damped and clamped. Needs the loop gateware image, switched to automatically. Poll with loop_probe, move the input with loop_input, stop with dac_stop.

NameTypeReqDescription
curve––Transfer function: DAC output codes indexed by input (1-2048 points, spread over the input range).
input_codeinteger––
input_map–––
kinteger–Damping, Q15 (32767 = jump straight to the target).
pointsinteger––
sharpnessnumber–Knee sharpness of the panel preset.
source––adc = closed loop; fixed = hold input_code (open loop); sweep = advance by step each tick.
stepinteger––
switch_imageboolean–If the pod is on the other gateware image, switch it first (~3 s). The switch resets the FPGA, stopping any DAC output, UART session or sensor emulation. false = fail instead.
tick_divinteger––
vmaxinteger––
vmininteger––
voc_code––Instead of curve: solar-panel I-V preset with this open-circuit code.
NameTypeReqDescription
armedbooleanyes–
curve_pointsintegeryes–
input_codeintegeryes–
kintegeryes–
source–yes–
stepintegeryes–
switched_image––The gateware image this call switched the pod to; null when no switch was needed.
tick_divintegeryes–
vmaxintegeryes–
vminintegeryes–

No examples provided.

current_out ~309

Hold a current on the 4-20 mA output (terminal J9), in amps, or read the range it can do. The output is loop powered: it needs an external floating supply on J9 (pin 1 plus to the supply plus, pin 2 through the receiver to the supply minus; 8 V plus 20 mA times the loop resistance, 30 V at most). Nothing in the loop may touch pod ground, also not through a target that shares a ground with the pod. Ask the user how J9 is wired before driving it. Never wire J9 straight into J8. The pod cannot see the loop: the call succeeds with the supply off. It cannot go below its live zero (a little above 0.004 A) or above about 0.0201 A: there is no 0 mA or 21 mA level. 0.004 gives the lowest current; anything else outside the range fails with the pod's message. The DAC is shared: this switches the 3v3/5v/12v outputs off, and dac_output, generate and replay also move the loop current. dac_stop leaves the loop where it was: set 0.004 to go back to 4 mA.

NameTypeReqDescription
current––Loop current to hold, in AMPS: 0.004 to 0.020 (0.012 is 12 mA). Omit to only read the range.
NameTypeReqDescription
code–yesThe 16-bit DAC code holding it; null when only the range was read.
current–yesLoop current now held on the 4-20 mA output, in amps; null when only the range was read.
max_currentnumberyesHighest current the output can do, in amps (about 0.0201).
min_currentnumberyesLowest current the output can do, in amps (its live zero, a little above 0.004).

No examples provided.

dac_output ~65

Route a DAC output (3v3, 5v, 12v = ±12 V, or off) and drive a calibrated DC voltage on it.

NameTypeReqDescription
pathstringyes–
volts––Calibrated DC volts to drive; omit to only route.
NameTypeReqDescription
code–yesThe DAC level as an 8-bit code (0..255); null when only routing.
code16––The full 16-bit DAC code (firmware 3.8.1 and later); null when only routing or on older firmware.
pathstringyes–
voltage–yesVoltage produced; null when only routing.

No examples provided.

dac_stop ~65

Stop any DAC output: generator, replay or control loop. The 4-20 mA output follows the DAC, so after a waveform on current_out the loop stays where it stopped: call current_out(0.004) to return it to 4 mA.

Input schema present but exposes no named parameters.

NameTypeReqDescription
stoppedboolean––

No examples provided.

decode_la ~558

Decode I2C (sda, scl), UART (rx, baud), SPI (sclk + mosi/miso/cs, mode), USB (dp, dm, speed), Modbus RTU (rx, baud, tx), CAN/CAN FD (can, bitrate, data_bitrate), PWM (channels), 1-Wire (onewire) or SMBus/PMBus (sda, scl, pec) from LA data. Sample at least ~10x the bit rate; USB full speed needs a 48 MS/s capture, low speed 6 MS/s; CAN 6 samples per data bit; 1-Wire 1 MS/s (4 MS/s in overdrive). USB items are transactions (token, data, handshake; repeated NAKs merged), transfers the control transfers with the SETUP request and descriptors decoded (an enumeration). Decoding the last capture again with other channels is free.

NameTypeReqDescription
baud–––
bitrate––can: nominal bit rate, bit/s.
can––can: the transceiver's RXD (or the controller's TX/RX).
capturestring–last = decode the previous capture_la; new = capture first (needs samples/sample_rate_hz).
channels––pwm: the channels to measure.
cs–––
data_bitrate––can: CAN FD data bit rate, bit/s (left out: the nominal rate).
dm––usb: the channel on D-.
dp––usb: the channel on D+.
max_itemsinteger––
miso–––
modeinteger––
mosi–––
onewire––onewire: the bus line.
pecstring–smbus/pmbus: auto = a trailing byte that matches is a PEC; on = every transaction ends in one.
protocolstringyes–
rx–––
sample_point––can: where a bit is read, as a fraction of it (default 0.75).
sample_rate_hznumber––
samplesinteger––
scl–––
sclk–––
sda–––
servoboolean–pwm: also read the high pulses as servo positions (1 ms = 0 %, 2 ms = 100 %).
speedstring–usb: full (12 Mbit/s), low (1.5 Mbit/s) or auto (from the idle state).
tx––modbus: the other direction on a two-line tap (rx alone for an RS-485 receive output).
NameTypeReqDescription
countintegeryes–
errors––USB, Modbus, CAN, 1-Wire, SMBus/PMBus: packets, frames or transactions with an error.
itemsarrayyes–
protocolstringyes–
sof_count––USB only: start-of-frame packets (left out of items).
speed––USB only: full or low.
text––UART only: the decoded bytes as text.
transfers––USB only: one line per control transfer (request, status, descriptor read back).
truncatedbooleanyes–

No examples provided.

delete_wiring ~57

Delete one of the pod's stored profiles. Ask the user first. The default cannot be deleted (BP0013): make another one the default first.

NameTypeReqDescription
namestringyesThe pod profile to delete (not the default).
NameTypeReqDescription
autosaveboolean–The server saves set_wiring's profile on the pod (--wiring-autosave).
board_header––The pod's I/O header: 'j1' (2x11 pin headers, one-piece boards up to v3-r2) or 'front' (2x13 connector on the front of digital v3r3 and later); null when the pod cannot tell.
default_profile––The pod's default profile.
directions––'sent' when the pod has the profile's pin directions (la_dir: sent on connect and by set_wiring), else 'not sent: <why>' (older firmware, or a DUT output pin driven right now).
efuse–yesTarget-power rail the tools default to: internal 5 V (efuse 1) or external (efuse 2); null when the profile sets none (pass efuse).
header_map––The profile on that header as text: each header pin in its physical place, then what to connect to each pin on the user's board. Show it to the user when they ask how to wire the board; both headers…
hint––What to do next about saving, when anything.
i2c_address–yesThe profile's I2C address (i2c_addr) as a 7-bit integer; null when unset.
la_voltage–yesLA I/O-bank voltage the profile asks for, in volts; null when it sets none.
pinsarrayyesLA1-LA14 with what is wired to each and its bias resistor.
profileobject–The profile as its JSON object.
profile_namestring–The pod profile this connection uses ('' when it came from elsewhere).
profile_revinteger–That profile's revision on the pod when it was loaded.
profilesarray–The profiles stored on the pod: [{name, rev, bytes}]. Empty on firmware that stores none.
savedboolean–This call stored the profile (on the pod, or on embeddedci.com for older firmware).
signalsarray––
sourcestringyesWhere the profile came from: pod (a profile stored on the pod), file (BENCHPOD_WIRING), dict (set_wiring, not saved), server (older firmware: the profile on embeddedci.com) or undefined (nothing is w…
swd_nresetbooleanyes–
swd_targetstringyes–
uart_baudintegeryes–
unsaved_changesarray–Keys of this connection's profile that differ from the copy stored on the pod: lost on disconnect unless saved (save_wiring).
versioninteger––
warningsarray–Wiring that works but is risky (e.g. an I2C bus with no pull-up).

No examples provided.

disconnect ~26

Close UART/CAN sessions and the connection, releasing a cloud lease. Safe when not connected.

Input schema present but exposes no named parameters.

NameTypeReqDescription
capabilities–––
connectedbooleanyes–
connection–––
eth_mac––The pod's Ethernet MAC (aa:bb:cc:dd:ee:ff), for a network that hands out addresses only to registered devices; null when not known (firmware 3.10.7 and older over the LAN).
firmwareobject–The pod's raw status report.
kind––tcp, serial (USB console), usb_net ('usb' reached the pod's USB network adapter), discover or embeddedci (cloud).
la_voltage––Selected LA bank voltage; null = not set.
leasedboolean–This session holds an exclusive lease: the server's on a cloud device, or the pod's own lease on the LAN or USB network.
local_lease––The pod's own lease (held, holder, purpose, left_s, mine), on firmware with the lease feature; null otherwise.
session–––
warningsarray––
wifi_mac––The MAC the pod uses on Wi-Fi; null on a pod without Wi-Fi, or until the pod scanned for Wi-Fi or joined a network. Over the cloud both come from embeddedci.com's record of the pod.
wiring_source––Where this connection's wiring profile came from: server (stored on embeddedci.com, as the web UI's Wiring tab shows it), file (BENCHPOD_WIRING), dict (set_wiring) or defaults.

No examples provided.

expansion ~598

Attach an I2C/SPI GPIO expander board, report it, or detach it. Attaching checks the LA voltage, probes the chip, puts every pin in input and names the pins EXT1..EXTn. Then gpio_mode, gpio_write, gpio_read, gpio_wait and gpio_release take 'EXTn' (or the names) next to LA channels; a write to several EXT pins is one bus transaction per chip. EXT pins are not FPGA-timed: gpio_pulse, la_step, capture triggers and la_dir refuse them. The expander's bus closes on its own before flash, i2c_open and SPI tools; i2c_open on the same two pins shares the bus with it.

NameTypeReqDescription
addr––I2C chips: the 7-bit address (default the chip's first, 0x20 = 32), or a list for several chips on one bus (EXT pins in that order). mcp23s17: hardware address 0-7.
chip––The expander chip to attach: tca9555, pca9555, mcp23017, pcf8574, pcf8574a, pcf8575, tca6416a, tca6424a, mcp23s17, 74hc595, 74hc165. Omit for the status (what is attached, its pins' modes and live le…
count––74hc595 / 74hc165: chips in the chain (8 pins each).
detachboolean–Detach the expander: every EXT pin back to input, its bus released.
hz––Bus clock; default 400 kHz for I2C (100 kHz pcf8574), 1 MHz for SPI.
load––74hc165 only: the LA channel on SH/LD, pulsed low before each read.
names––Names for the pins, {'EXT1': 'LED1', ...}; usable wherever EXTn is.
pullups––I2C pull-ups: pod (LA1-LA6 only, pull to the LA voltage, switched on here) or external (the breakout's). Default pod on LA1-LA6 when the pod has pull-ups at this voltage (1.8 V: firmware newer than 3…
scl––I2C SCL; omit for the wiring's i2c_scl.
sda––I2C SDA; omit for the wiring's i2c_sda.
spi––SPI chips: [sck, mosi, miso, cs]; omit for the wiring's spi_* roles. All four are needed: a 74hc595's MISO and a 74hc165's MOSI are free pins.
NameTypeReqDescription
addrs–––
attachedbooleanyes–
bus––i2c or spi.
chip–––
chips––The chips that can be attached, when none is.
count––Chips in a shift-register chain.
hz–––
la––The LA channels it uses: sda/scl, or sck/mosi/miso/cs (+ load for a 74hc165).
notes–––
pins–––
pullups––pod, external, or null for SPI.

No examples provided.

flash ~902

Program the DUT over SWD through the pod's CMSIS-DAP probe. Give either `file` (a path on this server's host) or an uploaded build (`build`, or `repo`/`ref` for the newest build of a branch). OpenOCD runs on this server's host, except for an uploaded build on a cloud connection, which embeddedci.com flashes itself. The SWD pins, the reset flag and the target config come from the wiring profile when omitted. A failed flash is a normal result (ok=false): read target_unreachable (unpowered, mis-wired or held in reset), stalled, and the log tails to decide what to change; `artifact` says which build was flashed. With target 'esp32' (any ESP32-family name) the pod writes `file` through the target's UART ROM bootloader instead: TXD0 on `rx`, RXD0 on `tx`, IO0 on `boot`, EN on the pod's reset pin (`nreset`); `file` is a .bin written at `load_address` (default 0) or an ESP-IDF flasher_args.json. No OpenOCD or esptool needed; works over the cloud too. stdout_tail names the chip and each region written; `reset` false leaves the target in its loader.

NameTypeReqDescription
artifactstring–With build: the file to flash when the build holds several (default: its .elf, then .hex, then .bin).
boot––ESP32 only: LA channel (or wiring name) wired to the target's IO0 (IO9 on the C3/C6); omit for a profile signal named BOOT, IO0 or IO9.
buildstring–Flash a build uploaded to embeddedci.com instead of a file: its build id (the upload's build_id output), or 'latest' for the newest one that matches repo/ref.
connect_attemptsinteger––
connect_under_reset–––
extra_args–––
extra_configs–––
filestring–Firmware image path on the machine running this server. Leave empty to flash an uploaded build instead (build/repo/ref/artifact). For an ESP32: a .bin written at 0 (esptool merge_bin) or an ESP-IDF b…
load_addressstring–Load address for raw .bin images, e.g. 0x08000000.
nreset––The target's reset line is wired to the pod's reset pin: enables connect-under-reset. Omit for the profile's swd_nreset.
refstring–With build: the branch or tag of the uploaded build, e.g. 'main'.
repostring–With build: the GitHub repository of the uploaded build, 'owner/name'.
resetboolean––
rx––ESP32 only: LA channel (or wiring name) wired to the target's TXD0; omit for the profile's uart_rx.
server_side––With build: true has embeddedci.com run OpenOCD (the default on an 'embeddedci:<pod>' connection), false downloads the file and runs OpenOCD here (the default on LAN/USB).
swclk––LA channel (or wiring name) wired to the DUT's SWCLK; omit for the profile's swd_swclk.
swdio––LA channel (or wiring name) wired to the DUT's SWDIO; omit for the profile's swd_swdio.
targetstring–OpenOCD target config, e.g. target/stm32f4x.cfg; omit for the profile's swd_target. 'esp32' (or esp32s3, esp32c3, ...) flashes an ESP32-family target over its UART ROM bootloader instead of SWD.
target_power––Power this rail on before flashing: internal 5 V (efuse 1) or external (efuse 2).
timeout_snumber––
tx––ESP32 only: LA channel (or wiring name) wired to the target's RXD0; omit for the profile's uart_tx.
verifyboolean––
NameTypeReqDescription
artifact–––
okbooleanyes–
returncodeintegeryes–
stalledbooleanyes–
stderr_tailstringyes–
stdout_tailstringyes–
target_unreachablebooleanyes–

No examples provided.

fpga_image ~140

Reprogram the pod's FPGA with another stored gateware image (~2-3 s). Rarely needed: control_loop and replay switch automatically (also back from the emulation image once no I2C/SPI/UART sensor runs). The pod never switches back by itself, and refuses to leave the emulation image while I2C/SPI/UART sensors run (sensor_stop first). The switch resets the FPGA (any DAC output or UART session stops).

NameTypeReqDescription
imagestringyesloop = control-loop image; deep_replay = deep DAC replay from PSRAM; emulation = sensor emulation (sensor_start loads it by itself).
NameTypeReqDescription
featuresintegeryes–
imagestringyes–
versionintegeryes–

No examples provided.

generate ~381

Drive a sine, square or sawtooth on a DAC output. The pod takes the volts, calibrates them for dac_path and plays the waveform at the DAC's full 16 bits; both peaks must be on the path. dac_path current_out plays it as a current on the 4-20 mA output (J9), with amplitude and offset in amps and steps of about 0.25 uA. See current_out for the wiring it needs. The DAC voltage outputs are switched off for it. dac_stop then leaves the loop where the waveform stopped: call current_out(0.004) to go back to 4 mA.

NameTypeReqDescription
amplitudenumberyesPeak volts. On dac_path current_out: peak AMPS (0.006 = 6 mA).
dac_path––DAC output. Omitted: 3v3, the lowest voltage output (with route false: the output last routed, cal1 = 5v). Pick the one the DUT pin tolerates: 5v and 12v can damage a 3.3 V pin.
duration_s––Seconds; omit to run until dac_stop.
freq_hznumberyes–
offset––Center volts; default mid-range of dac_path. On current_out: center AMPS (0.012 = 12 mA).
on_captureboolean–Start on the next capture's hardware t0 (phase-locked).
routeboolean–Route dac_path first. false = keep the current analog path (e.g. after analog_path('cal1') for a DAC-to-ADC loopback); dac_path then only sets the volts scaling.
sample_rate_hz––Sample rate in Hz; omit for the device maximum.
waveformstringyes–
NameTypeReqDescription
cotrigbooleanyes–
dac_pathstringyes–
freq_hznumberyes–
waveformstringyes–

No examples provided.

gpio_mode ~213

Claim LA channels as GPIO so the pod can drive or read them. A channel stays GPIO — across disconnects — until gpio_release, and while it is GPIO nothing else can use it: release it before uart_open, flash or sensor_start on that channel. A channel already owned by another function is refused with a PinConflictError naming the owner and the tool that frees it, and an engaged bias resistor that would fight the mode with a PullConflictError.

NameTypeReqDescription
laarrayyesLA channels as numbers 1-14 or wiring-profile names, and expander pins 'EXT1'..'EXTn' (or their names) once an expander is attached (expansion).
level––Starting level of an output (default 0) or open-drain channel (default 1, released). Not allowed for input.
modestring–output = push-pull; open_drain = 0 pulls low and 1 releases; input = high-Z, level readable.
NameTypeReqDescription
pinsarrayyesThe channels this call configured or released (expander pins as their EXT state).

No examples provided.

Install

How do I install the EmbeddedCI BenchPod MCP server?

EmbeddedCI BenchPod runs locally as a PyPI package, launched with uvx embeddedci-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · embeddedci-mcp

# add to Claude Code
claude mcp add embeddedci-com-embeddedci-mcp -- uvx embeddedci-mcp
Common questions

What is the EmbeddedCI BenchPod MCP server?

EmbeddedCI BenchPod is an MCP server listed in the public MCP registry as io.github.embeddedci-com/embeddedci-mcp. Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic. This page covers its PyPI package (embeddedci-mcp).

Is the EmbeddedCI BenchPod MCP server safe to use?

EmbeddedCI BenchPod scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the EmbeddedCI BenchPod MCP server expose?

EmbeddedCI BenchPod exposes 111 tools: connect, disconnect, status, set_la_voltage, wiring, and 106 more. Their descriptions and schemas cost roughly 18,376 tokens of context every time the server is loaded.

Is the EmbeddedCI BenchPod MCP server still maintained?

EmbeddedCI BenchPod is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the EmbeddedCI BenchPod MCP server under?

EmbeddedCI BenchPod declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the EmbeddedCI BenchPod MCP server?

VerifyMCP ran 15 checks on EmbeddedCI BenchPod, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about EmbeddedCI BenchPod: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.