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 (15 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
gpio_pulse ~191

Emit FPGA-timed pulses on an LA channel — a trigger for the DUT, or a step/dir motor train. The channel must be free or a GPIO output at level 0 (it returns to its GPIO level afterwards). The FPGA runs the train by itself, so this returns as soon as it starts.

NameTypeReqDescription
countinteger–Number of pulses (at most 65535).
la–yesLA channel 1-14, or a name from the wiring profile — a signal ('READY') or a role ('uart_rx', 'i2c_sda', 'swd_swclk'). Call `wiring` to see the names. The gpio_* tools also take expander pins ('EXT1'…
width_snumberyesSeconds the pulse is high (and low between pulses), 4 us to 65.535 ms.
NameTypeReqDescription
countintegeryes–
laintegeryes–
widthnumberyesSeconds each pulse is high (and low between pulses).

No examples provided.

gpio_read ~104

The live level (0/1) of LA channels and expander pins — omit `la` for all 14 LA channels and every EXT pin. Works whatever owns a channel; a GPIO input is the usual way to watch a DUT output.

NameTypeReqDescription
la––LA channels as numbers 1-14 or wiring-profile names, and expander pins 'EXT1'..'EXTn' (or their names) once an expander is attached (expansion).
NameTypeReqDescription
levelsarrayyes–

No examples provided.

gpio_release ~117

Stop using channels as GPIO — they go back to high-Z, watched by captures (EXT pins: input). Omit `la` to release every GPIO channel and EXT pin (channels owned by other functions are left alone). Do this before starting a UART session, flashing or emulating a sensor on those channels.

NameTypeReqDescription
la––LA channels as numbers 1-14 or wiring-profile names, and expander pins 'EXT1'..'EXTn' (or their names) once an expander is attached (expansion).
NameTypeReqDescription
releasedarrayyesChannels released; empty list = every GPIO channel and every EXT pin.

No examples provided.

gpio_wait ~178

Wait until an LA channel or EXT pin reads `level` (reached=false when timeout_s passes first). Polled from this host, so it resolves to a few milliseconds plus the round trip — for precise timing use a triggered capture (capture_la trigger_la) and la_timing instead.

NameTypeReqDescription
la–yesLA channel 1-14, or a name from the wiring profile — a signal ('READY') or a role ('uart_rx', 'i2c_sda', 'swd_swclk'). Call `wiring` to see the names. The gpio_* tools also take expander pins ('EXT1'…
levelinteger–0 = low; 1 = high (open_drain: released).
timeout_snumber–Seconds to wait.
NameTypeReqDescription
la–yes–
levelintegeryes–
reachedbooleanyesFalse means the timeout passed without the channel reaching level.
waitednumberyesSeconds spent waiting.

No examples provided.

gpio_write ~140

Set the level of GPIO output / open-drain channels (LA channels in one pod command per level; EXT pins in one bus transaction per expander chip). The channels must already be in an output or open_drain mode (gpio_mode).

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–yes0 = low; 1 = high (open_drain: released). One level for every channel, or a list with one level per channel.
NameTypeReqDescription
laarrayyes–
level–yes–

No examples provided.

i2c_close ~24

Release the I2C master's pins (safe when none is open).

Input schema present but exposes no named parameters.

NameTypeReqDescription
hz––SCL rate the pod runs; a real bus is somewhat slower (the rise time adds to each period).
openbooleanyes–
pullups–––
scl–––
sda–––

No examples provided.

i2c_open ~188

Make the pod an I2C master on two LA pins (gateware v55+), replacing any open session. Then i2c_transfer, i2c_scan, or capture_la with send. SWD, SPI and I2C exclude each other. "i2c busy" means another connection (the desktop app, the web app, a script) holds the pod's I2C master: close it there.

NameTypeReqDescription
hzinteger–SCL rate.
pullupsstring–pod: channels with the pod's pull-up on (set_pull(pull="up") first, LA1-LA6 today); external: the board has its own.
scl––SCL channel; omit for the profile's i2c_scl.
sda––SDA channel; omit for the profile's i2c_sda.
NameTypeReqDescription
hz––SCL rate the pod runs; a real bus is somewhat slower (the rise time adds to each period).
openbooleanyes–
pullups–––
scl–––
sda–––

No examples provided.

i2c_scan ~35

Which addresses answer on the open I2C session.

NameTypeReqDescription
endinteger––
startinteger––
NameTypeReqDescription
foundarrayyes7-bit addresses that answered.
found_hexarrayyes–

No examples provided.

i2c_transfer ~98

Write, read, or write then read on the open I2C session. Neither = a probe. A NACK is not an error: ack is false and nack_at says which byte.

NameTypeReqDescription
addrintegeryes7-bit address.
readinteger–Bytes to read after a repeated START.
write_hexstring–Bytes to write, hex (up to 128), e.g. a register.
NameTypeReqDescription
ackbooleanyesEvery byte was acknowledged.
addrintegeryes–
nack_at––When ack is false: 0 = the address, 1..N = the Nth written byte, N+1 = the read address.
rx_hexstring–The bytes read.

No examples provided.

la_dir ~146

Tell the pod which way each pin's DUT signal goes, so it never drives against a DUT output. connect and set_wiring already send the wiring profile's directions (firmware 3.10.4+); use this for a pin the profile doesn't name. The pod forgets them on a reboot.

NameTypeReqDescription
dir––Which way the DUT signal goes. On dut_output the pod refuses push-pull drivers.
from_wiringboolean–Send the wiring profile's directions again (each role's and signal's default, or the profile's dut_dirs).
la––Channels or wiring names, or 'all'. Omit with dir to list every pin.
NameTypeReqDescription
pinsarrayyesThe channels this call configured or released (expander pins as their EXT state).

No examples provided.

la_pins ~108

What owns each of the 14 LA channels — none (free), gpio, uart_rx/uart_tx, swd_clk/swd_dio, i2c_sda/i2c_scl or step — plus each channel's GPIO mode, commanded level and bias resistor. Read this when a tool is refused with a pin conflict: it names the owner to stop. Live pin levels come along when the gateware can read them. Captures observe every channel whatever owns it.

Input schema present but exposes no named parameters.

NameTypeReqDescription
levels––Live pin levels; null when the gateware cannot read them (no gpio_read capability).
pinsarrayyes–

No examples provided.

la_step ~175

Emit step pulses on an LA channel (step/dir motor drivers); with dir_la, set direction first. The step rate is 1 / (2 x delay_s). The FPGA runs the train by itself; this returns as soon as it starts. More than 65535 steps: send several trains (wait for the pod between them).

NameTypeReqDescription
delay_snumberyesHALF the step period in seconds: each pulse is high for delay_s, then low for delay_s, so pulses are 2 x delay_s apart. 4 us to 65.535 ms.
dir_la–––
directioninteger––
laintegeryesLA channel (1-14) the signal is wired to.
stepsintegeryesNumber of step pulses (at most 65535).
NameTypeReqDescription
delaynumberyes–
laintegeryes–
statusstring––
stepsintegeryes–

No examples provided.

la_timing ~164

Timing of one channel of the last capture_la / capture_correlated: edge timestamps, pulse widths, frequency and duty cycle; with to_la, the delay from its first edge to the next edge on to_la (e.g. a trigger pin to a "result ready" pin). Resolution is one sample; no new capture is taken.

NameTypeReqDescription
afternumber–Ignore edges earlier than this many seconds into the capture.
edgestring–Which transitions to list and to time the delay from.
laintegeryesLA channel (1-14) the signal is wired to.
max_edgesinteger––
to_edgestring––
to_la––Also measure the delay to the next to_edge on this channel.
NameTypeReqDescription
delay––Seconds from the first `edge` on la (at or after `after`) to the next `to_edge` on to_la; null when to_la is not given or either edge is missing.
duty_cyclenumberyes–
edgestringyes–
edge_timesarrayyesEdge timestamps in seconds from the capture start.
frequency_hz––From the rising edges; null with fewer than two.
high_pulses–yes–
laintegeryes–
low_pulses–yes–
resolutionnumberyesTimestamp resolution in seconds (one sample).
to_la–––
truncatedbooleanyesMore edges exist than edge_times lists.

No examples provided.

lan_tls ~192

The pod's LAN API over TLS: port 8443 (this server's default for a LAN address), HTTPS-only, and the certificate clients pin (sha256). Connections to a network address use TLS by default when the pod has it. Installing your own certificate: `benchpod lan-tls set-cert` or the SDK's set_lan_tls_cert.

NameTypeReqDescription
https_only––Omit to read. True: the pod refuses plaintext port 8080 on Ethernet and Wi-Fi, so only TLS (8443) crosses the LAN; its USB link keeps 8080. False turns it back off, which the pod only takes over TLS,…
regenerateboolean–True: the pod makes a new key and self-signed certificate. Clients that pinned the old one must trust the new one (`benchpod lan-tls trust`); this server's pin follows.
NameTypeReqDescription
connected_over_tlsboolean–Whether this MCP server's connection to the pod uses TLS.
errorstring–Why there is no certificate in use.
https_onlybooleanyesTrue: plaintext 8080 is refused on Ethernet and Wi-Fi (the USB link keeps it).
keystring–The key type, e.g. "EC P-256".
not_afterstring–Valid until (YYYY-MM-DD).
originstring–"generated" (the pod made it) or "user" (installed).
portintegeryesThe TLS port (8443).
sanarray–The certificate's DNS names.
sessionsintegeryesTLS connections open now (at most 2).
sha256string–SHA-256 of the certificate: the value clients pin.
subjectstring–The certificate's subject.

No examples provided.

list_waveforms ~28

The organisation's cloud waveform library (needs a cloud connection or BENCHPOD_API_KEY).

Input schema present but exposes no named parameters.

NameTypeReqDescription
waveformsarrayyes–

No examples provided.

load_wiring ~66

Switch this connection to one of the pod's stored profiles (nothing on the pod changes). Use it when the user says the bench is wired for another board, or after a BP0009 conflict.

NameTypeReqDescription
name––The pod profile to use; omit for the pod's 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.

log_level ~110

Read or set how much the pod prints on its USB console (firmware newer than 3.10.12). info is the default; debug also prints every command trace and the retry detail of the cloud, Wi-Fi and DHCP loops on the pod's console; warn and error print less. It changes only the console, never a tool's result.

NameTypeReqDescription
level––Omit to read the level. Set one to change it; the pod stores it across reboots and firmware updates.
NameTypeReqDescription
levelstringyes"error", "warn", "info" (the default) or "debug". Stored on the pod.

No examples provided.

loop_input ~45

Re-target the running loop's input without re-arming (hold a point, meter, move on).

NameTypeReqDescription
input_code–––
source–––
step–––
NameTypeReqDescription
input_codeintegeryes–
output_codeintegeryes–
source–yes–
stepintegeryes–

No examples provided.

loop_probe ~29

The running loop's live operating point; assert against loop_input, not i, in open-loop runs.

Input schema present but exposes no named parameters.

NameTypeReqDescription
iintegeryesLatest raw ADC reading.
input_code–yes–
loop_inputintegeryesThe value the loop indexed the curve with.
source–yes–
vintegeryesDAC code driven this tick.

No examples provided.

measure_power ~213

Measure the DUT's supply current and voltage for a window: average, minimum and peak current, voltage, energy and charge (gap-free sampling, so energy is integrated, not estimated). Use this for a self-contained window (a boot, a sleep interval). To profile across other tool calls, bracket them with power_profile_start / power_profile_stop.

NameTypeReqDescription
duration_snumberyesSeconds to sample (blocking).
efuse––Target-power rail: internal 5 V (efuse 1) or external (efuse 2). Omit for the wiring profile's rail.
pointsinteger–Points of current/voltage trace to return alongside the statistics; 0 = statistics only.
rate_hznumber–Samples per second. Accurate to ~200 Hz; above that the pod delivers what its sampling loop allows, flattening near 365 Hz. rate_hz in the result is what you actually got, adc_rate_hz what the sensor…
NameTypeReqDescription
adc_rate_hznumber–Conversion rate the current sensor was configured for — the ceiling, not what arrived.
avg_currentnumberyes–
avg_powernumberyesWatts (energy over duration).
avg_voltagenumberyes–
chargenumberyesCoulombs.
durationnumberyes–
efuseintegeryesThe rail used: internal 5 V (efuse 1) or external (efuse 2).
energynumberyesJoules, integrated over every sample.
faultbooleanyesThe eFuse tripped (over-current or short) during the profile.
max_voltagenumberyes–
min_currentnumberyes–
min_voltagenumberyes–
nintegeryesRaw samples the statistics cover.
peak_currentnumberyes–
rate_hznumberyesSamples per second actually delivered (measured). The pod reads one sensor register per firmware pass, so this lands below what was asked for — roughly 350-450 Hz. Every sample carries its own timest…
trace_currentarray–Amps per trace point.
trace_stepnumber–Seconds covered by each trace point.
trace_voltagearray–Volts per trace point.
truncatedbooleanyesSampling stopped at max_duration rather than on request.

No examples provided.

power_cycle_and_capture ~300

Power the target off, then capture UART while it powers back on — the boot banner lands in the window. The channels, baud, frame (parity, stop bits) and power rail come from the wiring profile when omitted.

NameTypeReqDescription
baud––UART baud rate; omit for the wiring profile's uart_baud.
delay_snumber–Seconds into the capture the power comes back.
duration_snumber–Capture window in seconds; must exceed delay_s.
efuse––Target-power rail: internal 5 V (efuse 1) or external (efuse 2). Omit for the wiring profile's rail.
off_settle_snumber––
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.

power_off ~74

Switch the target's power rail off. The result says which rail was used.

NameTypeReqDescription
delay_s––Seconds: schedule the power-off pod-side.
efuse––Target-power rail: internal 5 V (efuse 1) or external (efuse 2). Omit for the wiring profile's rail.
NameTypeReqDescription
delay–––
efuseintegeryesThe rail used: internal 5 V (efuse 1) or external (efuse 2).
la_voltage––The I/O voltage the profile set before power-on.
onbooleanyes–
profile––The wiring profile the board was powered on with.

No examples provided.

power_on ~203

Power the board on with its wiring profile applied first: the profile's I/O voltage is set (when the pod has none or another one), its pull resistors (pulls; at 1.8 V only on firmware newer than 3.10.12) are set, then the rail goes on, and the pod records the profile. The result names the rail, the profile and the I/O voltage. Never changes the I/O voltage under a board that is already powered.

NameTypeReqDescription
delay_s––Seconds: schedule the power-on pod-side and return at once (e.g. to power on during a capture).
efuse––Target-power rail: internal 5 V (efuse 1) or external (efuse 2). Omit for the wiring profile's rail.
wiring_profile––A stored wiring profile to power the board with (it becomes this connection's profile); omit to use the current one.
NameTypeReqDescription
delay–––
efuseintegeryesThe rail used: internal 5 V (efuse 1) or external (efuse 2).
la_voltage––The I/O voltage the profile set before power-on.
onbooleanyes–
profile––The wiring profile the board was powered on with.

No examples provided.

power_profile_start ~128

Start sampling the target-power rail in the background, then run the steps you want to profile and call power_profile_stop. Replaces any profile already running.

NameTypeReqDescription
efuse––Target-power rail: internal 5 V (efuse 1) or external (efuse 2). Omit for the wiring profile's rail.
max_duration_snumber–Seconds after which the pod stops sampling by itself (the result is then truncated).
rate_hznumber–Samples per second; accurate to ~200 Hz, flattening near 365 Hz above that.
NameTypeReqDescription
efuseintegeryesThe rail used: internal 5 V (efuse 1) or external (efuse 2).
max_durationnumberyesSeconds after which the pod stops sampling by itself.
rate_hznumberyesSample rate asked for; the achieved rate is in the stop result.
runningboolean––

No examples provided.

power_profile_stop ~52

Stop the running power profile and return its statistics (and, with points, a trace).

NameTypeReqDescription
pointsinteger–Points of current/voltage trace to return alongside the statistics; 0 = statistics only.
NameTypeReqDescription
adc_rate_hznumber–Conversion rate the current sensor was configured for — the ceiling, not what arrived.
avg_currentnumberyes–
avg_powernumberyesWatts (energy over duration).
avg_voltagenumberyes–
chargenumberyesCoulombs.
durationnumberyes–
efuseintegeryesThe rail used: internal 5 V (efuse 1) or external (efuse 2).
energynumberyesJoules, integrated over every sample.
faultbooleanyesThe eFuse tripped (over-current or short) during the profile.
max_voltagenumberyes–
min_currentnumberyes–
min_voltagenumberyes–
nintegeryesRaw samples the statistics cover.
peak_currentnumberyes–
rate_hznumberyesSamples per second actually delivered (measured). The pod reads one sensor register per firmware pass, so this lands below what was asked for — roughly 350-450 Hz. Every sample carries its own timest…
trace_currentarray–Amps per trace point.
trace_stepnumber–Seconds covered by each trace point.
trace_voltagearray–Volts per trace point.
truncatedbooleanyesSampling stopped at max_duration rather than on request.

No examples provided.

power_status ~45

Both target-power rails, internal 5 V (efuse 1) and external (efuse 2): on/off and tripped state, bus voltage and current draw.

Input schema present but exposes no named parameters.

NameTypeReqDescription
external–yesThe external rail (efuse 2).
internal–yesThe internal 5 V rail (efuse 1).
pod––The pod's own draw; null on boards that don't measure it.

No examples provided.

pull_status ~37

Every LA channel's pull resistor: state (up, down or off), the directions it supports (empty without a resistor) and its value.

Input schema present but exposes no named parameters.

NameTypeReqDescription
channelsarrayyes–

No examples provided.

replay ~482

Loop a waveform out of the DAC until dac_stop: agent-provided volts, the last ADC capture, or a waveform from the cloud library (waveform_id). More than 2048 samples need the deep_replay gateware image, switched to automatically (a library waveform with target_samples is downsampled instead). dac_path current_out replays on the 4-20 mA output (J9) in amps. A last capture of current_in, or a library recording with unit mA, replays as the same current; a voltage recording there needs mapping fit. See current_out for the wiring. After dac_stop, call current_out(0.004) to go back to 4 mA.

NameTypeReqDescription
dac_path––DAC output. Omitted: 3v3, the lowest voltage output (with route false: the output last routed, cal1 = 5v; for waveform_id: the waveform's own, else 3v3). Pick the one the DUT pin tolerates: 5v and 12…
fault–––
from_last_captureboolean–Replay the last capture_adc instead of volts.
mappingstring–faithful = reproduce volts (clip); fit = auto-scale.
on_captureboolean––
routeboolean–Route dac_path first (false = keep the current analog path).
sample_rate_hz––Replay rate; defaults to the capture's own rate.
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.
target_samplesinteger–waveform_id: downsample a shallow replay to this many samples.
volts––Waveform in volts, one value per sample. On dac_path current_out the values are AMPS (0.004 to 0.020).
waveform_id––Instead of volts: a waveform from the cloud library (list_waveforms; needs server access).
window_leninteger–waveform_id: samples to replay; 0 = to the end.
window_startinteger–waveform_id: first recording sample to replay.
NameTypeReqDescription
cotrigbooleanyes–
dac_pathstringyes–
deepbooleanyes–
sample_rate_hznumberyes–
samplesintegeryes–
switched_image––The gateware image this call switched the pod to; null when no switch was needed.

No examples provided.

reset_target ~80

Drive the DUT's reset line from the pod's reset pin (rev3 pods, DUT header J1 pin 22).

NameTypeReqDescription
actionstring–pulse = reset once; hold = keep the target in reset; release = let it run; status = read only.
pulse_snumber–Pulse length in seconds (at most 1).
NameTypeReqDescription
assertedbooleanyes–
supportedboolean––

No examples provided.

save_capture_as_recording ~87

Save the last capture_adc to the cloud waveform library as a replayable recording. A capture of current_in (the 4-20 mA input) is stored as a current, unit mA; full_scale_v is then in mA too.

NameTypeReqDescription
full_scale_v––Volts the top code represents; default the peak.
namestringyes–
NameTypeReqDescription
idstringyes–
kindstringyes–
namestringyes–
sample_countintegeryes–

No examples provided.

save_wiring ~152

Store a wiring profile on the pod, where the web app, CI and every other connection see it. Ask the user first: saving changes what everyone uses. Saving the profile this connection loaded fails with BP0009 when someone else saved it meanwhile (load_wiring shows their version). Saving never changes the pod's default profile (set_default_wiring does).

NameTypeReqDescription
name––The pod profile to store it as (1-40 characters: a-z, 0-9, -). Default: the profile this connection loaded, else the pod's default. Use a new name for a different board.
profile––A full profile to store instead of this connection's (schema version 2).
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.

sensor_capture ~175

Wait for the DUT's next transaction on an I2C sensor's bus (up to 2 s), capture it from its START and decode it into a transaction trace (S/Sr/P, addr, data, ACK). A quiet bus is a trigger timeout error. Firmware without the sensor_la_trigger capability captures at once instead. I2C only: capture an SPI or UART sensor's pins with capture_la.

NameTypeReqDescription
address––Also report whether the DUT addressed this device.
instancestringyesInstance name, 1 to 16 lowercase letters, digits or _; sensor_start defaults it to the definition's name (pass one when that name is longer).
register––With address: the bytes the DUT read from this register.
samplesinteger–Packed bytes to capture (4 samples each).
NameTypeReqDescription
addressed–––
addressesarrayyes–
register_value–––
tracestringyes–
transactionsintegeryes–
truncatedbooleanyes–

No examples provided.

sensor_fault ~227

Make a running sensor misbehave now, to test the DUT's error handling.

NameTypeReqDescription
at––corrupt: the register.
duration_s––Omit to last until sensor_fault_clear.
instancestringyesInstance name, 1 to 16 lowercase letters, digits or _; sensor_start defaults it to the definition's name (pass one when that name is longer).
mask––corrupt: the XOR mask.
param––The param a stuck/offset/gain fault applies to.
rate_hz––garbage: bytes per second (default 100).
typestringyesstuck (readings freeze), offset/gain (param + value), no_response (I2C NACK, SPI MISO released, UART silent), corrupt (register at XOR mask), bus_stuck (I2C SDA low, at most 1 s), garbage/drop/baud_e…
value––offset/gain amount, drop probability, baud error percent, or a stuck/open/short value.
NameTypeReqDescription
replyobject––

No examples provided.

sensor_fault_clear ~64

End a sensor's faults (injected with sensor_fault or by the stimulus).

NameTypeReqDescription
instancestringyesInstance name, 1 to 16 lowercase letters, digits or _; sensor_start defaults it to the definition's name (pass one when that name is longer).
NameTypeReqDescription
replyobject––

No examples provided.

sensor_format ~82

The sensor definition and stimulus format (Markdown): read it before writing a definition from a datasheet. Needs no pod.

NameTypeReqDescription
version––Sensor library version: 'latest', a release such as '0.2.0', or 'default' (the version the SDK pins). Sets it for the other sensor tools too. Omit to keep the current one.
NameTypeReqDescription
textstringyes–

No examples provided.

sensor_library ~188

The sensor library: ready definitions the pod can emulate (name, kind, label) and the version in use. Sensor flow: sensor_library -> sensor_show(name) for its params -> set_la_voltage and, for I2C, set_pull(pull="up") on SDA/SCL -> sensor_start(definition=name, pins) -> sensor_set / sensor_fault / sensor_stimulus_load + sensor_stimulus_start -> sensor_status, sensor_regs -> sensor_stop. No library entry for the part? Write a definition from its datasheet (sensor_format) and pass the YAML to sensor_validate, then sensor_start. Needs no pod.

NameTypeReqDescription
version––Sensor library version: 'latest', a release such as '0.2.0', or 'default' (the version the SDK pins). Sets it for the other sensor tools too. Omit to keep the current one.
NameTypeReqDescription
entriesarrayyespath, name, kind (i2c/spi/uart/analog/stimulus), label.
sourcestringyesbundled (shipped with the SDK), cache or download.
versionstringyesThe library version the sensor tools use.
warningstring–Why a fallback version is used (offline, say); empty otherwise.

No examples provided.

sensor_regs ~105

The bytes an I2C/SPI sensor answers now (the DUT's own writes included).

NameTypeReqDescription
instancestringyesInstance name, 1 to 16 lowercase letters, digits or _; sensor_start defaults it to the definition's name (pass one when that name is longer).
length––Bytes to read; omit for the rest of the image.
startinteger–Offset in the 256-byte register image (i2c.page is its window).
NameTypeReqDescription
bytesarrayyes–
startintegeryes–

No examples provided.

sensor_set ~120

Change what a running sensor reports; the DUT sees it on its next read or message. Out-of-range values are refused with the range.

NameTypeReqDescription
instancestringyesInstance name, 1 to 16 lowercase letters, digits or _; sensor_start defaults it to the definition's name (pass one when that name is longer).
valuesobjectyesParam key -> value, e.g. {"temperature_c": 31.5}; the keys, units and ranges are the definition's params (sensor_show, or the params sensor_start returns).
NameTypeReqDescription
replyobject––

No examples provided.

sensor_show ~102

One library definition: its YAML (a starting point for your own part) and the params sensor_set takes. Needs no pod.

NameTypeReqDescription
namestringyesLibrary entry name ('sht4x') or path.
version––Sensor library version: 'latest', a release such as '0.2.0', or 'default' (the version the SDK pins). Sets it for the other sensor tools too. Omit to keep the current one.
NameTypeReqDescription
kindstringyes–
labelstringyes–
namestringyes–
paramsarrayyeskey, unit, min, max, default: what sensor_set takes.
pathstringyes–
versionstringyes–
yamlstringyesThe definition as stored in the library.

No examples provided.

sensor_start ~453

Make the pod play a sensor for the DUT: upload the definition (library name or your own YAML/JSON) and start it on pins. Set the LA voltage first, and the pull-ups for I2C (set_pull(la=[sda, scl], pull="up"), LA1-LA6). Starting an instance name that runs replaces it. Up to 4 I2C sensors (several may share one bus at different addresses), 1 SPI, 1 UART and 2 analog sensors (one per output) run at once. I2C/SPI/UART sensors load the pod's emulation FPGA image if another runs (image_loaded in the result); it stays after sensor_stop, and control_loop / deep replays switch back by themselves once no I2C/SPI/UART sensor runs. Pod limits: UART 8N1 only, one FIFO sensor at a time, conversion/command times at most 65.535 ms (4 distinct per I2C sensor), no excitation: adc. The result lists the params sensor_set takes.

NameTypeReqDescription
address––I2C: the definition's address or one of its alt_addresses (0x77 or "0x77"); omit for its address.
baud––UART: override the definition's baud rate.
definition–yesA library sensor name ('bme280', see sensor_library), a .yaml/.json path on the machine running this server, the definition itself as YAML or JSON text, or a JSON object. Write your own from a datash…
instance–––
pins––Role -> LA channel (1-14) or wiring name. I2C: sda, scl (default: the profile's i2c_sda/i2c_scl), optional drdy. SPI: sclk, mosi, miso, cs (default: the profile's spi_*; no data-ready pin). UART: tx…
values––Initial param values; omitted ones start at their defaults.
NameTypeReqDescription
infoobjectyesThe pod's compile report.
instancestringyes–
kindstringyes–
namestringyes–
paramsarrayyeskey, unit, min, max, default: what sensor_set takes.
startedobjectyesThe start reply: slot, image, image_loaded (the emulation FPGA image was loaded), unavailable.

No examples provided.

sensor_status ~48

Running sensors (slot, pins, values, faults with left_s, bus counters: writes and last_write say the DUT talked to it; transfers is always null), the stimulus and the FPGA image.

Input schema present but exposes no named parameters.

NameTypeReqDescription
replyobject––

No examples provided.

sensor_stimulus_load ~109

Upload values over time (and timed faults) for the running sensors; replaces the loaded stimulus. sensor_stimulus_start plays it.

NameTypeReqDescription
stimulus–yesA stimulus (kind: stimulus): YAML or JSON text, a JSON object, or a path on the machine running this server. Signals are params ('temperature_c', or 'env.temperature_c' with several sensors); segment…
NameTypeReqDescription
replyobject––

No examples provided.

sensor_stimulus_start ~56

Play the loaded stimulus; it ends after its last segment (signals hold their last value) unless it has repeat: true.

NameTypeReqDescription
at_s––Start this many seconds into the stimulus; omit for t = 0.
NameTypeReqDescription
replyobject––

No examples provided.

sensor_stimulus_stop ~23

Stop the stimulus; the values stay where it left them.

Input schema present but exposes no named parameters.

NameTypeReqDescription
replyobject––

No examples provided.

sensor_stop ~49

Stop a sensor (or all): the pod releases its pins and forgets the definition. The emulation FPGA image stays loaded.

NameTypeReqDescription
instance––The instance to stop; omit to stop every sensor.
NameTypeReqDescription
instancesarray–The instances the pod stopped.
stoppedboolean––

No examples provided.

sensor_validate ~145

Check a definition: its header here, then a dry-run compile on the pod (nothing is kept). Without a connected pod only the header (format, kind, name, params, size) is checked. A compile error names the place, e.g. "registers[4].s16be: unknown name 'ax' at 17": fix it and validate again.

NameTypeReqDescription
definition–yesA library sensor name ('bme280', see sensor_library), a .yaml/.json path on the machine running this server, the definition itself as YAML or JSON text, or a JSON object. Write your own from a datash…
NameTypeReqDescription
checkedstringyesheader (no pod connected: header and size only) or pod (compiled on the pod).
kindstringyes–
namestringyes–
okbooleanyes–
reportobject–The pod's compile report: params, program_bytes, bus settings.

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.