EmbeddedCI BenchPod
PYPI · EMBEDDEDCI-MCP
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
Available components
Last scanned (15 hours ago)
Scores higher than 71% of PyPI servers
Category IoT and Hardware
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
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 →
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
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 →
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 →
set_default_wiring ~46
Make a stored profile the pod's default (ask the user: it changes what everyone gets).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The pod profile every connection uses when it names none. |
| Name | Type | Req | Description |
|---|---|---|---|
| autosave | boolean | – | 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 | – | yes | Target-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 | – | yes | The profile's I2C address (i2c_addr) as a 7-bit integer; null when unset. |
| la_voltage | – | yes | LA I/O-bank voltage the profile asks for, in volts; null when it sets none. |
| pins | array | yes | LA1-LA14 with what is wired to each and its bias resistor. |
| profile | object | – | The profile as its JSON object. |
| profile_name | string | – | The pod profile this connection uses ('' when it came from elsewhere). |
| profile_rev | integer | – | That profile's revision on the pod when it was loaded. |
| profiles | array | – | The profiles stored on the pod: [{name, rev, bytes}]. Empty on firmware that stores none. |
| saved | boolean | – | This call stored the profile (on the pod, or on embeddedci.com for older firmware). |
| signals | array | – | – |
| source | string | yes | Where 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_nreset | boolean | yes | – |
| swd_target | string | yes | – |
| uart_baud | integer | yes | – |
| unsaved_changes | array | – | Keys of this connection's profile that differ from the copy stored on the pod: lost on disconnect unless saved (save_wiring). |
| version | integer | – | – |
| warnings | array | – | Wiring that works but is risky (e.g. an I2C bus with no pull-up). |
No examples provided.
set_la_voltage ~265
Select the LA I/O-bank voltage to match the DUT's I/O (1.8 V needs a rev3 pod, 5.0 a digital v3r4 board). Usually not needed: connect sets it from the wiring profile's la_mv, and firmware 3.10.10+ takes it from the profile on the first LA operation. Call it when the profile sets none (ask the user), or to override the profile for this session. At 5.0 outputs reach 5 V only through their pull-ups: switch on the pull-up (set_pull up) on outputs into 5 V CMOS-level inputs. Point the user to https://embeddedci.com/docs/benchpod-targets/5v-rs485#5v-io for the details. On digital v3r4 the result has pin21; when its state is high, tell the user a DUT signal is above the I/O voltage (select 5.0 or remove the signal).
| Name | Type | Req | Description |
|---|---|---|---|
| la_voltage | – | – | The DUT's I/O voltage. 5.0 needs a pod with the digital board v3r4 (status capabilities vref_out). Omit it to read the current voltage and pin 21 without changing anything. |
| Name | Type | Req | Description |
|---|---|---|---|
| pin21 | – | – | Digital v3r4 only: J1 pin 21. |
| readback | – | – | – |
| voltage | – | yes | – |
No examples provided.
set_pull ~174
Pull LA channels up or down, or switch their pull resistor off. For an I2C bus pull SDA and SCL up. The pull-ups pull to the LA voltage (1.8 V or 3.3 V).
| Name | Type | Req | Description |
|---|---|---|---|
| la | array | yes | LA channels (1-14). |
| pull | string | yes | The direction: up, down or off. The pod picks the resistor from the pin's function (ohms and strength in the result). A channel pulls only the ways its resistor allows (pull_status: supported): on th… |
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | yes | – |
No examples provided.
set_wiring ~348
Replace the wiring profile this connection uses. It is NOT stored on the pod unless save is true (or the server autosaves): the result's unsaved_changes and hint say what is not stored. The profile is validated first: two roles or signals on one LA channel, an out-of-range pin or an unknown key are rejected with a message naming every problem. Autosave never stores a change of the I/O voltage, the power rail or the SWD target: call save_wiring for those.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | object | yes | The profile as a JSON object (schema version 2): la_mv, efuse, uart_rx/uart_tx/uart_baud, i2c_sda/i2c_scl/i2c_addr, swd_swclk/swd_swdio/swd_nreset/swd_target, spi_*, and signals [{name, la, direction… |
| save | boolean | – | Also store it on the pod (as save_wiring does). Default false: this connection only, unless the server runs with --wiring-autosave. |
| Name | Type | Req | Description |
|---|---|---|---|
| autosave | boolean | – | 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 | – | yes | Target-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 | – | yes | The profile's I2C address (i2c_addr) as a 7-bit integer; null when unset. |
| la_voltage | – | yes | LA I/O-bank voltage the profile asks for, in volts; null when it sets none. |
| pins | array | yes | LA1-LA14 with what is wired to each and its bias resistor. |
| profile | object | – | The profile as its JSON object. |
| profile_name | string | – | The pod profile this connection uses ('' when it came from elsewhere). |
| profile_rev | integer | – | That profile's revision on the pod when it was loaded. |
| profiles | array | – | The profiles stored on the pod: [{name, rev, bytes}]. Empty on firmware that stores none. |
| saved | boolean | – | This call stored the profile (on the pod, or on embeddedci.com for older firmware). |
| signals | array | – | – |
| source | string | yes | Where 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_nreset | boolean | yes | – |
| swd_target | string | yes | – |
| uart_baud | integer | yes | – |
| unsaved_changes | array | – | Keys of this connection's profile that differ from the copy stored on the pod: lost on disconnect unless saved (save_wiring). |
| version | integer | – | – |
| warnings | array | – | Wiring that works but is risky (e.g. an I2C bus with no pull-up). |
No examples provided.
spi_flash_info ~221
Read the JEDEC ID of the SPI NOR flash on the SPI pins (gateware v45+, capability spi_master). present=false means the ID read all 00 or all FF: nothing is answering (wiring, power, or /WP and /HOLD not tied high). The pins are released again afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| cs | – | – | LA channel (or wiring name) for CS; omit for the profile's spi_cs. |
| hz | integer | – | SCK rate; rounded down to what the pod can do. |
| miso | – | – | LA channel (or wiring name) for MISO (the chip's DO); omit for the profile's spi_miso. |
| mode | integer | – | SPI mode; 1 and 2 need gateware v55+. |
| mosi | – | – | LA channel (or wiring name) for MOSI (the chip's DI); omit for the profile's spi_mosi. |
| sck | – | – | LA channel (or wiring name) for SCK; omit for the profile's spi_sclk. |
| Name | Type | Req | Description |
|---|---|---|---|
| hz | integer | yes | – |
| jedec_id | string | yes | – |
| present | boolean | yes | – |
| size | integer | yes | – |
| status | integer | yes | – |
No examples provided.
spi_flash_program ~318
Erase, write and verify an image into the SPI NOR flash wired to the SPI pins. 25-series parts, first 16 MB. Throughput is roughly 30 KB/s over the LAN (erase is extra) and slower over the cloud. Fails with the pod's message when nothing answers, the part is write-protected, or a chunk does not verify.
| Name | Type | Req | Description |
|---|---|---|---|
| addr | integer | – | Flash address to write the image at. |
| cs | – | – | LA channel (or wiring name) for CS; omit for the profile's spi_cs. |
| erase | boolean | – | Erase the 4 KB sectors the image covers first. |
| file | string | yes | Image path on the machine running this server (raw binary). |
| hold_reset | boolean | – | Hold the DUT in reset for the job (its controller then cannot drive the same bus); released after. |
| hz | integer | – | – |
| miso | – | – | LA channel (or wiring name) for MISO (the chip's DO); omit for the profile's spi_miso. |
| mode | integer | – | SPI mode; 1 and 2 need gateware v55+. |
| mosi | – | – | LA channel (or wiring name) for MOSI (the chip's DI); omit for the profile's spi_mosi. |
| sck | – | – | LA channel (or wiring name) for SCK; omit for the profile's spi_sclk. |
| verify | boolean | – | The pod reads every chunk back and fails on a difference. |
| Name | Type | Req | Description |
|---|---|---|---|
| addr | integer | yes | – |
| erased | integer | yes | – |
| jedec_id | string | yes | – |
| length | integer | yes | – |
| seconds | number | yes | – |
| verified | boolean | yes | – |
No examples provided.
spi_flash_read ~213
Read bytes back from the SPI NOR flash, to a file or (up to 4096 bytes) as hex.
| Name | Type | Req | Description |
|---|---|---|---|
| addr | integer | yes | – |
| cs | – | – | LA channel (or wiring name) for CS; omit for the profile's spi_cs. |
| file | string | – | Write the bytes to this path on the server's machine; omit to get up to 4096 bytes back as hex. |
| hz | integer | – | – |
| length | integer | yes | – |
| miso | – | – | LA channel (or wiring name) for MISO (the chip's DO); omit for the profile's spi_miso. |
| mode | integer | – | SPI mode; 1 and 2 need gateware v55+. |
| mosi | – | – | LA channel (or wiring name) for MOSI (the chip's DI); omit for the profile's spi_mosi. |
| sck | – | – | LA channel (or wiring name) for SCK; omit for the profile's spi_sclk. |
| Name | Type | Req | Description |
|---|---|---|---|
| addr | integer | yes | – |
| file | string | – | – |
| hex | string | – | – |
| length | integer | yes | – |
No examples provided.
spi_transfer ~212
One full-duplex SPI transaction (CS asserted for all of tx) with any SPI device on the SPI pins. Returns what came back on MISO. The SPI master is armed for the call and released after it.
| Name | Type | Req | Description |
|---|---|---|---|
| cs | – | – | LA channel (or wiring name) for CS; omit for the profile's spi_cs. |
| hz | integer | – | – |
| miso | – | – | LA channel (or wiring name) for MISO; omit for the profile's spi_miso. |
| mode | integer | – | SPI mode; 1 and 2 need gateware v55+. |
| mosi | – | – | LA channel (or wiring name) for MOSI; omit for the profile's spi_mosi. |
| sck | – | – | LA channel (or wiring name) for SCK; omit for the profile's spi_sclk. |
| tx_hex | string | yes | Bytes to send, as hex (e.g. 9f000000 reads a JEDEC ID). Up to 4096 bytes. |
| Name | Type | Req | Description |
|---|---|---|---|
| hz | integer | yes | – |
| rx_hex | string | yes | – |
No examples provided.
status ~44
Connection, firmware, capabilities, selected LA voltage and open sessions — with warnings for anything that will block the next steps (e.g. no LA voltage). Works when not connected.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | – | – | – |
| connected | boolean | yes | – |
| 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). |
| firmware | object | – | 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. |
| leased | boolean | – | 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 | – | – | – |
| warnings | array | – | – |
| 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.
uart_close ~20
Stop the background UART session (safe when none is open).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| baud | – | – | – |
| half_duplex | boolean | – | – |
| open | boolean | yes | – |
| parity | – | – | – |
| rx | – | – | – |
| stop_bits | – | – | – |
| tx | – | – | – |
No examples provided.
uart_open ~597
Start buffering the DUT's UART in the background (replacing any open session). Open it BEFORE an action whose output matters (power_on, reset_target), then uart_read; use uart_write to type into the DUT's console. The channels and baud come from the wiring profile when omitted; the result says which were used. So do parity and stop_bits (8N1 unless the profile says otherwise). The LA pins are 1.8/3.3 V only: a 5 V UART needs a level shifter and an RS-485 bus (Modbus RTU) an external RS-485 transceiver in between. A channel used as GPIO must be released first (gpio_release). half_duplex runs the session on one wire (rx; tx defaults to it), and entry runs a pod-timed boot-mode entry before it starts (reset with TX held low, release, the first bytes), for boot-ROM programming such as RL78 TOOL0. de puts an RS-485 transceiver's DE on an LA channel the pod switches itself while it sends.
| Name | Type | Req | Description |
|---|---|---|---|
| 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_low | boolean | – | Drive DE low while sending (an active-low enable). |
| 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_duplex | boolean | – | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| baud | – | – | – |
| half_duplex | boolean | – | – |
| open | boolean | yes | – |
| parity | – | – | – |
| rx | – | – | – |
| stop_bits | – | – | – |
| tx | – | – | – |
No examples provided.
uart_read ~65
Return the UART output received since the previous uart_read, optionally waiting for a match.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_s | number | – | Seconds to wait for until_regex (or, without one, for any new output). |
| until_regex | – | – | Python regular expression; stop as soon as it matches. |
| Name | Type | Req | Description |
|---|---|---|---|
| closed | boolean | yes | – |
| matched | – | – | Whether until_regex matched (null without one). |
| overflowed | boolean | yes | – |
| text | string | yes | Everything received since the previous uart_read. |
| truncated | boolean | yes | – |
No examples provided.
uart_write ~41
Send text to the DUT's RX through the open UART session.
| Name | Type | Req | Description |
|---|---|---|---|
| line_ending | string | – | Appended after text. |
| text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| written | integer | yes | – |
No examples provided.
usb_network ~111
Read the pod's USB network setting, or turn the adapter off. Only the device changes it: Ethernet, Wi-Fi and the cloud may only read it.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | – | – | Omit to read the setting. false turns the pod's USB network adapter off (only over the pod's USB network link: connection 'usb'); the pod then re-enumerates as its USB console only and this connectio… |
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | Whether the pod's USB port is also a network adapter. |
| note | string | – | What happens next, after a change. |
No examples provided.
vision_add_reference ~83
Store the current screen (or a region of it, e.g. an icon as a template) as a reference.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| name | string | yes | – |
| overwrite | boolean | – | – |
| region | – | – | [x, y, w, h] in screen pixels (camera pixels before calibration). Omit for the whole screen. |
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| name | string | yes | – |
| size | – | – | – |
No examples provided.
vision_calibrate ~114
Map camera pixels to screen pixels; every later box and tap is in screen pixels.
| Name | Type | Req | Description |
|---|---|---|---|
| corners | – | – | The screen's top-left, top-right, bottom-right, bottom-left corners in camera pixels (read them from vision_look(space='camera')). Or omit and use method. |
| method | – | – | auto: find the bright screen (show white on it); markers: the screen shows markers.png. |
| screen_size | – | – | The screen's own resolution [w, h], e.g. [1920, 720]. |
| Name | Type | Req | Description |
|---|---|---|---|
| corners | array | yes | – |
| method | string | yes | – |
| quality | number | yes | – |
| screen_size | array | yes | – |
No examples provided.
vision_cloud_boards ~68
The AI Vision boards registered to your embeddedci.com organisation, and whether each is online. Connect to one with vision_connect(connection) using its `connection` ('embeddedci:<name>'). Authenticates with BENCHPOD_API_KEY, else the `benchpod login` session.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| boards | array | yes | – |
No examples provided.
vision_compare ~62
How close the screen is to a stored reference screen.
| Name | Type | Req | Description |
|---|---|---|---|
| mask | – | – | Areas to ignore: names of the reference's masks ('clock') or [x, y, w, h]. |
| reference | string | yes | Name of a reference screen (vision_add_reference). |
| Name | Type | Req | Description |
|---|---|---|---|
| changed_pct | number | yes | – |
| reference | string | yes | – |
| score | number | yes | 0..1; 1 = identical to the reference. |
No examples provided.
vision_connect ~151
Open the AI Vision connection (closing a previous one) and report the board's status.
| Name | Type | Req | Description |
|---|---|---|---|
| connection | – | – | host[:port] or URL of the ai-vision-2 board, 'discover' (mDNS), or 'embeddedci:<name>' for a board on embeddedci.com (vision_cloud_boards lists them). Omit for AIVISION_CONNECTION. |
| lease_as | – | – | Take the board's lease under this name, so nobody else drives the camera or the actuator until vision_disconnect. |
| token | – | – | The board's API token on the LAN; omit for AIVISION_TOKEN. Over embeddedci.com the `benchpod login` session or BENCHPOD_API_KEY is used instead. |
| Name | Type | Req | Description |
|---|---|---|---|
| actuators | array | – | – |
| calibrated | boolean | – | – |
| camera_locked | – | – | – |
| capabilities | array | – | – |
| connected | boolean | yes | – |
| lease | – | – | Who holds the board's lease, if anyone. |
| screen_size | – | – | – |
| url | string | – | – |
| version | string | – | – |
| warnings | array | – | – |
No examples provided.
vision_disconnect ~23
Close the AI Vision connection and release its lease. Safe when not connected.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| actuators | array | – | – |
| calibrated | boolean | – | – |
| camera_locked | – | – | – |
| capabilities | array | – | – |
| connected | boolean | yes | – |
| lease | – | – | Who holds the board's lease, if anyone. |
| screen_size | – | – | – |
| url | string | – | – |
| version | string | – | – |
| warnings | array | – | – |
No examples provided.
vision_find ~117
Elements matching text, a kind or a template, best first. Text inside a button returns the button (its center is where a press taps).
| Name | Type | Req | Description |
|---|---|---|---|
| label | – | – | Element kind instead: button, icon, text. |
| match | – | – | How text is compared; default exact (case-insensitive). |
| region | – | – | [x, y, w, h] in screen pixels (camera pixels before calibration). Omit for the whole screen. |
| template | – | – | Name of a template reference instead. |
| text | – | – | Text to look for. |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| matches | array | yes | – |
No examples provided.
vision_look ~116
The screen as an image, so you can read it yourself. With a region: that part at full sensor resolution (small text, icons).
| Name | Type | Req | Description |
|---|---|---|---|
| overlay | – | – | Draw what the board recognised on the image. |
| region | – | – | [x, y, w, h] in screen pixels (camera pixels before calibration). Omit for the whole screen. |
| space | string | – | screen: the rectified screen in its own pixels (needs a calibration); camera: what the camera sees, to find the screen's corners. |
No output schema declared.
No examples provided.
vision_ocr ~72
All text on the screen (or a region) in reading order, with boxes.
| Name | Type | Req | Description |
|---|---|---|---|
| region | – | – | [x, y, w, h] in screen pixels (camera pixels before calibration). Omit for the whole screen. |
| zoom | – | – | Read at this many image pixels per screen pixel (small text). |
| Name | Type | Req | Description |
|---|---|---|---|
| frame_id | integer | yes | – |
| lines | array | yes | – |
| text | string | yes | – |
No examples provided.
vision_press ~124
Find the element, tap its center with the actuator, and optionally verify the result. Fails with the visible text when the element is not on the screen.
| Name | Type | Req | Description |
|---|---|---|---|
| actuator | – | – | Actuator id; omit for the first one. |
| match | – | – | How text is compared; default exact (case-insensitive). |
| text | string | yes | Text of the button or element to press. |
| verify_text | – | – | Then wait for this text to appear. |
| verify_timeout_s | number | – | Seconds to wait for verify_text; the board caps one request at 90 s. |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | string | – | – |
| found | – | – | – |
| tapped_at | – | – | – |
| verified | – | – | None when no verify condition was given. |
| verify_condition | string | – | – |
No examples provided.
vision_screen_health ~49
Black, dim, frozen, flickering or stuck pixels over a window of frames.
| Name | Type | Req | Description |
|---|---|---|---|
| expect_motion | boolean | – | Count a frozen screen as a problem. |
| window_ms | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| black | boolean | yes | – |
| dim | boolean | yes | – |
| flicker_hz | number | yes | – |
| frozen | boolean | yes | – |
| mean_luma | number | yes | – |
| ok | boolean | yes | – |
| problems | array | yes | – |
No examples provided.
vision_status ~33
Version, calibration, camera lock, actuators, lease and capabilities, with warnings for what will block the next steps.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| actuators | array | – | – |
| calibrated | boolean | – | – |
| camera_locked | – | – | – |
| capabilities | array | – | – |
| connected | boolean | yes | – |
| lease | – | – | Who holds the board's lease, if anyone. |
| screen_size | – | – | – |
| url | string | – | – |
| version | string | – | – |
| warnings | array | – | – |
No examples provided.
vision_tap ~66
Tap a point in screen pixels (hold_ms > 0 for a long press).
| Name | Type | Req | Description |
|---|---|---|---|
| actuator | – | – | Actuator id; omit for the first one. |
| hold_ms | integer | – | – |
| x | number | yes | Screen pixels. |
| y | number | yes | Screen pixels. |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | string | – | – |
| found | – | – | – |
| tapped_at | – | – | – |
| verified | – | – | None when no verify condition was given. |
| verify_condition | string | – | – |
No examples provided.
vision_wait_for ~107
Wait until text appears (or, with gone, disappears). Returns met=false on timeout.
| Name | Type | Req | Description |
|---|---|---|---|
| gone | boolean | – | Wait until the text has left the screen instead. |
| match | – | – | How text is compared; default exact (case-insensitive). |
| region | – | – | [x, y, w, h] in screen pixels (camera pixels before calibration). Omit for the whole screen. |
| text | string | yes | Text to wait for. |
| timeout_s | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | yes | – |
| elapsed_s | number | yes | – |
| match | – | – | – |
| met | boolean | yes | – |
No examples provided.
wiring ~180
Which DUT signal is on which LA channel — call this first, before any channel argument. Returns the profile this connection uses (normally a profile stored on the pod: profile_name, the pod's default unless connect named another): a 14-row pin table, the named signals, the power rail, the UART baud and the SWD target, warnings about risky wiring, the pod's stored profiles and unsaved_changes (what set_wiring changed that is not stored yet), and header_map: the profile on the pod's real I/O header as text, to show the user how to wire their board. Every tool whose channel, baud, rail or SWD arguments are omitted takes them from this profile; what the profile does not set is undefined, and a tool that needs it says so: ask the user, never guess a pin.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| autosave | boolean | – | 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 | – | yes | Target-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 | – | yes | The profile's I2C address (i2c_addr) as a 7-bit integer; null when unset. |
| la_voltage | – | yes | LA I/O-bank voltage the profile asks for, in volts; null when it sets none. |
| pins | array | yes | LA1-LA14 with what is wired to each and its bias resistor. |
| profile | object | – | The profile as its JSON object. |
| profile_name | string | – | The pod profile this connection uses ('' when it came from elsewhere). |
| profile_rev | integer | – | That profile's revision on the pod when it was loaded. |
| profiles | array | – | The profiles stored on the pod: [{name, rev, bytes}]. Empty on firmware that stores none. |
| saved | boolean | – | This call stored the profile (on the pod, or on embeddedci.com for older firmware). |
| signals | array | – | – |
| source | string | yes | Where 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_nreset | boolean | yes | – |
| swd_target | string | yes | – |
| uart_baud | integer | yes | – |
| unsaved_changes | array | – | Keys of this connection's profile that differ from the copy stored on the pod: lost on disconnect unless saved (save_wiring). |
| version | integer | – | – |
| warnings | array | – | Wiring that works but is risky (e.g. an I2C bus with no pull-up). |
No examples provided.
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
claude mcp add embeddedci-com-embeddedci-mcp -- uvx embeddedci-mcp
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.