USB Servo Controller
PYPI · UCAN-SERVO-MCP
Drive 12 hobby servos on an open-hardware USB-C controller: moves, poses, sequences, rail current
Available components
Last scanned (5 hours ago)
Scores higher than 55% 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 Security49
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 954 tokens (~59/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (38% 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
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
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 pypi/ucan-servo-mcp@0.4.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Stale | 1 |
| No linked repository | 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 →
board_status ~39
Rail current/voltage, faults, protection limits, and every channel's name, mode, travel limits, speed and current position (0 = off).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
clear_faults ~26
Clear a latched overcurrent/undervoltage fault so channels can move again.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
disable_servos ~32
Stop driving the given channels (numbers or names); the servos go limp.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
go_to_pose ~41
Move to a saved pose (see list_poses) and wait until it arrives.
| Name | Type | Req | Description |
|---|---|---|---|
| duration_s | number | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
list_poses ~24
Poses and the sequence saved from the GUI (servogui.json).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
measure_current ~32
Sample the servo-rail current continuously; returns peak, mean and min mA.
| Name | Type | Req | Description |
|---|---|---|---|
| seconds | number | – | – |
No output schema declared.
No examples provided.
move_servos ~93
Move one or more servos and wait until they arrive. positions: {channel number or name: pulse width in us}, e.g. {"0": 1200}. duration_s: time for all to arrive together (0 = each channel's own speed). Positions are clamped to each channel's limits. Turns channels on if off.
| Name | Type | Req | Description |
|---|---|---|---|
| duration_s | number | – | – |
| positions | object | yes | – |
No output schema declared.
No examples provided.
play_sequence ~50
Play the GUI's saved sequence of poses (move and hold times as saved), repeated `loops` times. Stops early on a fault; capped at 120 s.
| Name | Type | Req | Description |
|---|---|---|---|
| loops | integer | – | – |
No output schema declared.
No examples provided.
read_analog ~41
Read channel 0-7 as an analog input (0-4095 counts, 0-3.3 V).
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | – |
No output schema declared.
No examples provided.
release_port ~41
Close the serial port now (servos keep holding) so the GUI or flash.py can use the board. It reopens automatically on the next tool call.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
run_script ~16
Start the stored script from the top.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
script_status ~22
What script is stored on the board, and whether it is running.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_protection ~65
Set the rail trip limits (0 disables either). Overcurrent is capped at 7500 mA: the board's continuous budget is ~5 A. Resets at power-up.
| Name | Type | Req | Description |
|---|---|---|---|
| overcurrent_ma | integer | yes | – |
| undervoltage_mv | integer | – | – |
No output schema declared.
No examples provided.
stop_all ~16
Panic stop: every channel off immediately.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
stop_script ~25
Stop the stored script; servos keep their positions (stop_all to let go).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
upload_script ~269
Compile a servo script and store it in the board's flash, where the firmware runs it without a PC (autorun: also start at every power-up). One statement per line; channels by number or name; times in ms or '1.5s': label: jump/loop target move <ch> <us> [<time>] ramp there; does not wait: moves on different channels run together, a repeat move of the same channel waits for the previous one pose <name> [<time>] move every channel of a GUI pose sync wait until all moves arrive wait <time> off <ch>|all loop <label> [<n>] block runs n times in total; no n = forever jump <label> waitin <ch> >|< <0-4095> wait for analog input ch (0-7) ifin <ch> >|< <0-4095> run next statement only if true end Positions are clamped to the channel limits. Max 254 instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| autorun | boolean | – | – |
| run | boolean | – | – |
| script | string | yes | – |
No output schema declared.
No examples provided.
How do I install the USB Servo Controller MCP server?
USB Servo Controller runs locally as a PyPI package, launched with uvx ucan-servo-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 · ucan-servo-mcp
claude mcp add lukasz-juranek-usb-servo-controller -- uvx ucan-servo-mcp
What is the USB Servo Controller MCP server?
USB Servo Controller is an MCP server listed in the public MCP registry as io.github.Lukasz-Juranek/usb-servo-controller. Drive 12 hobby servos on an open-hardware USB-C controller: moves, poses, sequences, rail current. This page covers its PyPI package (ucan-servo-mcp).
Is the USB Servo Controller MCP server safe to use?
USB Servo Controller scores 51 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 USB Servo Controller MCP server expose?
USB Servo Controller exposes 16 tools: board_status, move_servos, disable_servos, stop_all, list_poses, and 11 more. Their descriptions and schemas cost roughly 832 tokens of context every time the server is loaded.
Is the USB Servo Controller MCP server still maintained?
USB Servo Controller 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 USB Servo Controller MCP server under?
USB Servo Controller declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.