Gearotons M17 Servomotor
PYPI · SERVOMOTOR-MCP
Drive Gearotons M17 open-source servomotors from plain English over RS-485; mock mode, no hardware.
Available components
Last scanned (9 hours ago)
Scores higher than 87% of PyPI servers
Category IoT and Hardware
Recent critical change
GHSA-6q48-6c7w-9gw2 affects this package (21 Oct 2026). See the changelog before you install this server.
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
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Gearotons/servomotor-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 43 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 9480 tokens (~166/item across 57 items; 57 tools + 0 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 Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "run_sequence" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 57 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
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 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −5
- Stability: pass → 0.63 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 22 Oct 26 +88
- GHSA-6q48-6c7w-9gw2 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- Score status: failed → scored ▲ functional
- 21 Oct 26 −88
- GHSA-6q48-6c7w-9gw2 affects this package: none ▼ critical
- Known CVEs: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- 16 Oct 26 +39
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 12 Oct 26 −24
- Stability: 0.97 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified 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 5 Nov 2026 · Analysed pypi/servomotor-mcp@0.3.3
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 | Gearotons/servomotor-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Gearotons/servomotor-mcp/.github/workflows/publish.yml@refs/tags/v0.3.3 |
| Rekor log index | 2909271930 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:86007f99d87eef45b15f103b799a090e3b847fcc27afe12da7d68b05d1383996 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| 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 →
stop ~94
Immediately halt one motor, or ALL motors if ``motor`` is omitted. Use for "stop", "halt", or any sign something is wrong. Sends the firmware's emergency stop: the driver outputs turn OFF and the move queue empties, so there is NO holding torque afterwards and a load can move the shaft. Send ``enable_mosfets`` before commanding the next move.
| Name | Type | Req | Description |
|---|---|---|---|
| motor | – | – | – |
No output schema declared.
No examples provided.
system_reset ~161
System reset / go to the bootloader. The motor will reset immediately and will enter the bootloader. If there is no command sent within a short time, the motor will exit the bootloader and run the application from the beginning. [Firmware command "System reset", group: Basic Control.] NOTE: Reboots the motor (~2 s): position re-zeroes at the current shaft location, MOSFETs disable, fatal errors clear. Returns: success confirmation. motor: an alias number (e.g. 88), a 16-hex-digit unique ID (e.g. "0123456789ABCDEF"), or "all" to broadcast to every motor on the bus (broadcasts get no responses back).
| Name | Type | Req | Description |
|---|---|---|---|
| motor | string | yes | – |
No output schema declared.
No examples provided.
test_mode ~267
Set or trigger a certain test mode. This is a bit undocumented at the moment. Don't use this unless you are a developer working on test cases. Notable modes: 0 = clear all test modes; 1-9 = motor test modes; 10-13 = LED test modes (locks up the device); 14-73 = trigger fatal errors 0-59; 74 = set the overvoltage-protection threshold to 22 V (production test, should trip on a 24 V supply); 75 = set the overvoltage-protection threshold to 26 V (production test, should not trip on a 24 V supply). A system reset restores the default overvoltage threshold. [Firmware command "Test mode", group: Configuration.] NOTE: Developer/diagnostic modes; behavior depends on firmware internals. Parameters: - testMode: The test mode to use or trigger Returns: success confirmation. motor: an alias number (e.g. 88), a 16-hex-digit unique ID (e.g. "0123456789ABCDEF"), or "all" to broadcast to every motor on the bus (broadcasts get no responses back).
| Name | Type | Req | Description |
|---|---|---|---|
| motor | string | yes | – |
| testMode | integer | yes | – |
No output schema declared.
No examples provided.
time_sync ~185
Sends the master time to the motor so that it can sync its own clock (do this 10 times per second). [Firmware command "Time sync", group: Device Management.] Parameters: - masterTime (in seconds): The motor absolute time that the motor should sync to (in microseconds). Returns: - timeError: The error in the motor's time compared to the master time. - rccIcscr: The contents of the RCC-ICSCR register (holds the HSICAL and HSITRIM settings). motor: an alias number (e.g. 88), a 16-hex-digit unique ID (e.g. "0123456789ABCDEF"), or "all" to broadcast to every motor on the bus (broadcasts get no responses back).
| Name | Type | Req | Description |
|---|---|---|---|
| masterTime | number | yes | – |
| motor | string | yes | – |
No output schema declared.
No examples provided.
trapezoid_move ~208
Move immediately to the given position using the currently set speed (the speed is set by a separate command) [Firmware command "Trapezoid move", group: Motion Control.] NOTE: The displacement is RELATIVE to the current position. This QUEUES the move and returns immediately; poll get_n_queued_items for completion, or use move_to/move_relative which wait. Requires enable_mosfets first. Parameters: - displacement (in degrees): The displacement to travel. Can be positive or negative. - duration (in seconds): The time over which to do the move. Returns: success confirmation. motor: an alias number (e.g. 88), a 16-hex-digit unique ID (e.g. "0123456789ABCDEF"), or "all" to broadcast to every motor on the bus (broadcasts get no responses back).
| Name | Type | Req | Description |
|---|---|---|---|
| displacement | number | yes | – |
| duration | number | yes | – |
| motor | string | yes | – |
No output schema declared.
No examples provided.
vibrate ~133
Cause the motor to start to vary the voltage quickly and therefore to vibrate (or stop). [Firmware command "Vibrate", group: Device Management.] Parameters: - vibrationLevel: Vibration level (0 = turn off, 1 = turn on). Returns: success confirmation. motor: an alias number (e.g. 88), a 16-hex-digit unique ID (e.g. "0123456789ABCDEF"), or "all" to broadcast to every motor on the bus (broadcasts get no responses back).
| Name | Type | Req | Description |
|---|---|---|---|
| motor | string | yes | – |
| vibrationLevel | integer | yes | – |
No output schema declared.
No examples provided.
zero_position ~111
Make the current position the position zero (origin) [Firmware command "Zero position", group: Basic Control.] NOTE: Redefines the current shaft location as 0 degrees (no movement). Returns: success confirmation. motor: an alias number (e.g. 88), a 16-hex-digit unique ID (e.g. "0123456789ABCDEF"), or "all" to broadcast to every motor on the bus (broadcasts get no responses back).
| Name | Type | Req | Description |
|---|---|---|---|
| motor | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Gearotons M17 Servomotor MCP server?
Gearotons M17 Servomotor runs locally as a PyPI package, launched with uvx servomotor-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 · servomotor-mcp
claude mcp add gearotons-servomotor-mcp -- uvx servomotor-mcp
What is the Gearotons M17 Servomotor MCP server?
Gearotons M17 Servomotor is an MCP server listed in the public MCP registry as io.github.Gearotons/servomotor-mcp. Drive Gearotons M17 open-source servomotors from plain English over RS-485; mock mode, no hardware. This page covers its PyPI package (servomotor-mcp).
Is the Gearotons M17 Servomotor MCP server safe to use?
Gearotons M17 Servomotor scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Gearotons M17 Servomotor MCP server expose?
Gearotons M17 Servomotor exposes 57 tools: list_serial_ports, connect, disconnect, detect_devices, list_motors, and 52 more. Their descriptions and schemas cost roughly 9,480 tokens of context every time the server is loaded.
Is the Gearotons M17 Servomotor MCP server still maintained?
Gearotons M17 Servomotor 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 Gearotons M17 Servomotor MCP server under?
Gearotons M17 Servomotor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.