IterxAI CLI
NPM · @ITERX/CLI
IterxAI hardware toolchain for AI agents: parts, check, build, flash, sim, preview
Available components
Last scanned (6 hours ago)
Scores higher than 35% of npm 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 7 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1659 tokens (~97/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +3
- Stability: unverified → 0.23 ▲ functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 49
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@iterx/cli@0.7.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 1 package
| Packages resolved | 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 →
build_project ~47
Compile the project firmware and write build/receipt.json.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | – | Absolute path to the IterxAI project directory (contains iterx.json). Defaults to the server cwd. |
No output schema declared.
No examples provided.
check_project ~58
Validate an IterxAI project (manifest, selection, netlist, firmware). Errors include a fix hint.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | – | Absolute path to the IterxAI project directory (contains iterx.json). Defaults to the server cwd. |
No output schema declared.
No examples provided.
create_project ~179
Scaffold a new IterxAI hardware project (iterx.json, selection, netlist, src/main.ino, sim smoke scenario) plus agent config files. Use when the user has no project yet.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | Board id or alias, e.g. uno, esp32-devkit, esp32-s3, esp32-c3 (see get_rules topic "firmware"). Default arduino-uno. |
| dir | string | yes | New project directory (absolute, or relative to the server cwd). |
| dryRun | boolean | – | Only report the files that would be written. |
| harness | string | – | Comma-separated agents to configure: codex,claude,trae,workbuddy (default all). |
| name | string | – | Project display name. |
| recipe | string | – | Starter recipe (default blink). |
No output schema declared.
No examples provided.
doctor ~77
One-shot environment report: node, arduino-cli, cores, simulators, network, desktop bridge, login — each problem with a fix command.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | Optional board id to check. |
| projectPath | string | – | Absolute path to the IterxAI project directory (contains iterx.json). Defaults to the server cwd. |
No output schema declared.
No examples provided.
ensure_toolchain ~186
Install (or with check:true only report) a verified standalone toolchain: managed arduino-cli + board core + project libraries, plus IterxAI simulator components (QEMU / ESP-EMU) for ESP32 boards. Idempotent; works without the desktop app.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | Board id (e.g. arduino-uno, esp32-devkit, esp32-c3-generic); defaults to the project board. |
| check | boolean | – | Only report what is missing; download nothing. |
| projectPath | string | – | Absolute path to the IterxAI project directory (contains iterx.json). Defaults to the server cwd. |
| source | string | – | auto (default), arduino (compile toolchain only), iterx (simulator components only) or espressif (simulator components from Espressif's official QEMU release). |
No output schema declared.
No examples provided.
generate_board ~215
Generate the PCB with the IterxAI desktop board engine (same code as the desktop app; runs headless in the IterxAI runtime when the desktop is closed). mode: prototype adopts the first-version board (run once first), generate (default) lays out, autoroutes, runs DRC and writes Gerber/drill/JLC package, reroute re-routes the saved board, layout only places, board skips the JLC package. Gate failures (e.g. FIRMWARE_REVALIDATION_REQUIRED, PROTOTYPE_REQUIRED) keep the saved board and return error.fix with the next step.
| Name | Type | Req | Description |
|---|---|---|---|
| doubleSided | boolean | – | Allow components on both board sides. |
| handoffOnly | boolean | – | Only rebuild Gerber/JLC files from the saved board. |
| mode | string | – | Default generate. |
| process | string | – | Copper layers available to the router. |
| projectPath | string | – | Absolute path to the IterxAI project directory (contains iterx.json). Defaults to the server cwd. |
No output schema declared.
No examples provided.
get_help ~80
iterx CLI help as data: without `command`, every command grouped with exit codes, env vars and the JSON envelope; with `command`, its usage, options, examples and notes. Use it to discover CLI-only features (flash, monitor, preview).
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | – | Optional command name, e.g. "sim" or "parts". |
No output schema declared.
No examples provided.
get_part ~48
Get full facts for one part by id (pins, power, libraries).
| Name | Type | Req | Description |
|---|---|---|---|
| facts | array | – | Optional subset of facts to return. |
| id | string | yes | Part id from search_parts. |
No output schema declared.
No examples provided.
get_rules ~69
Get IterxAI project authoring rules (file layout, wiring, firmware conventions). Read before editing a project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | – | Absolute path to the IterxAI project directory (contains iterx.json). Defaults to the server cwd. |
| topic | string | – | Optional rules topic. |
No output schema declared.
No examples provided.
list_devices ~18
List connected serial devices/boards available for flashing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
project_status ~70
Project summary: board, selected parts, netlist size, file health, and whether build/receipt.json is fresh or stale. Call first to orient in a project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | – | Absolute path to the IterxAI project directory (contains iterx.json). Defaults to the server cwd. |
No output schema declared.
No examples provided.
render_wiring ~49
Render the project wiring diagram and return it as SVG text.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | – | Absolute path to the IterxAI project directory (contains iterx.json). Defaults to the server cwd. |
No output schema declared.
No examples provided.
search_parts ~82
Search the IterxAI parts catalog (boards, sensors, actuators). Returns matching parts with ids for get_part.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | Optional boardId to filter for compatibility. |
| limit | integer | – | Max results (default decided by CLI). |
| query | string | yes | Free-text query, e.g. "temperature sensor" or "ESP32". |
No output schema declared.
No examples provided.
sim_run ~101
Run the project in the simulator, optionally with a scenario file; assertion failures are reported as errors.
| Name | Type | Req | Description |
|---|---|---|---|
| duration | string | – | Simulated duration, e.g. "5s" or "2000ms". |
| projectPath | string | – | Absolute path to the IterxAI project directory (contains iterx.json). Defaults to the server cwd. |
| scenario | string | – | Scenario file path (sim/*.yaml|*.json), relative to the project. |
No output schema declared.
No examples provided.
sync_parts_catalog ~101
Download (or refresh) the signed IterxAI cloud parts catalog (~10 MB, the same catalog the desktop app uses). Call it when search_parts/get_part fail with PARTS_CATALOG_SYNCING or warn PARTS_CATALOG_STALE; it may take a few minutes on a slow link. Needs a signed-in IterxAI account like every iterx tool.
| Name | Type | Req | Description |
|---|---|---|---|
| refresh | boolean | – | Force a full re-download even if the cache is current. |
No output schema declared.
No examples provided.
sync_project ~53
Sync derived project files (selection/netlist/firmware stubs) after edits.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | – | Absolute path to the IterxAI project directory (contains iterx.json). Defaults to the server cwd. |
No output schema declared.
No examples provided.
whoami ~86
Show the IterxAI login state. iterx requires an IterxAI account: when logged out (LOGIN_REQUIRED warning) every tool except get_help/whoami/doctor fails until the user runs `iterx login` in a terminal (it opens a browser to register/sign in). Callable without login.
| Name | Type | Req | Description |
|---|---|---|---|
| offline | boolean | – | Only report the local token state (no network). |
No output schema declared.
No examples provided.
How do I install the IterxAI CLI MCP server?
IterxAI CLI runs locally as an npm package, launched with npx -y @iterx/cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @iterx/cli
claude mcp add jrenc2002-iterx -- npx -y @iterx/cli
What is the IterxAI CLI MCP server?
IterxAI CLI is an MCP server listed in the public MCP registry as io.github.jrenc2002/iterx. IterxAI hardware toolchain for AI agents: parts, check, build, flash, sim, preview. This page covers its npm package (@iterx/cli).
Is the IterxAI CLI MCP server safe to use?
IterxAI CLI scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 IterxAI CLI MCP server expose?
IterxAI CLI exposes 17 tools: search_parts, get_part, sync_parts_catalog, get_help, create_project, and 12 more. Their descriptions and schemas cost roughly 1,519 tokens of context every time the server is loaded.
Is the IterxAI CLI MCP server still maintained?
IterxAI CLI is still listed as active in the MCP registry. We last reached this channel on 5 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 IterxAI CLI MCP server under?
IterxAI CLI 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.