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.

Gearotons M17 Servomotor

PYPI · SERVOMOTOR-MCP · SCANNED SEP 20

Drive Gearotons M17 open-source servomotors from plain English over RS-485; mock mode, no hardware.

Available components

−10 this week 54 Trust /100
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 native-build step with no shell scripting around it. View diagnostics → Pass
  • 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 9467 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 Management37
  • Stability observed for 11 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
Install

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

# add to Claude Code
claude mcp add gearotons-servomotor-mcp -- uvx servomotor-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "gearotons-servomotor-mcp": {
      "command": "uvx",
      "args": [
        "servomotor-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "gearotons-servomotor-mcp": {
      "command": "uvx",
      "args": [
        "servomotor-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add gearotons-servomotor-mcp -- uvx servomotor-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gearotons-servomotor-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "servomotor-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add gearotons-servomotor-mcp --command uvx --arg servomotor-mcp
# ~/.hermes/config.yaml
mcp_servers:
  gearotons-servomotor-mcp:
    command: "uvx"
    args: ["servomotor-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "gearotons-servomotor-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "servomotor-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add gearotons-servomotor-mcp -t stdio -c uvx -a servomotor-mcp
// mcp.json
{
  "mcpServers": {
    "gearotons-servomotor-mcp": {
      "command": "uvx",
      "args": [
        "servomotor-mcp"
      ]
    }
  }
}
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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +4
    • Stability: unverified → 0.27 functional
  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 13 Sept 26 +15
    • Malware scan: unverified → pass security
  • 9 Sept 26 49

    First indexed and scored.

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 20 Sept 2026 · Analysed pypi/servomotor-mcp@0.3.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

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 29 packages
Packages resolved 29
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 57 exposed · ~9,467 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
stop ~81

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: motion halts and the move queue empties; holding torque remains. Use ``disable_mosfets`` afterwards to let the shaft spin freely.

NameTypeReqDescription
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).

NameTypeReqDescription
motorstringyes

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).

NameTypeReqDescription
motorstringyes
testModeintegeryes

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).

NameTypeReqDescription
masterTimenumberyes
motorstringyes

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).

NameTypeReqDescription
displacementnumberyes
durationnumberyes
motorstringyes

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).

NameTypeReqDescription
motorstringyes
vibrationLevelintegeryes

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).

NameTypeReqDescription
motorstringyes

No output schema declared.

No examples provided.

Common questions

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 54 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 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,467 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 20 September 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.