Sphero Rvr MCP Server

sphero-rvr-mcp PyPI v0.2.5

Published by jsperson — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for controlling Sphero RVR with Claude AI - featuring direct serial protocol for low-latency control

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 55

Each tool and what it can reach — statically extracted from the published source.

  • calibrate_magnetometerno sensitive capability
  • clear_emergency_stopno sensitive capability
  • connectno sensitive capability
  • connect_simpleno sensitive capability
  • disconnectno sensitive capability
  • drive_backwardno sensitive capability
  • drive_forwardno sensitive capability
  • drive_rcno sensitive capability
  • drive_tankno sensitive capability
  • drive_with_headingno sensitive capability
Show 45 more tools ↓
  • emergency_stopno sensitive capability
  • enable_color_detectionno sensitive capability
  • enable_motor_fault_notifyno sensitive capability
  • enable_motor_stall_notifyno sensitive capability
  • get_ambient_lightno sensitive capability
  • get_battery_statusno sensitive capability
  • get_battery_thresholdsno sensitive capability
  • get_battery_voltageno sensitive capability
  • get_battery_voltage_stateno sensitive capability
  • get_board_revisionno sensitive capability
  • get_color_detectionno sensitive capability
  • get_connection_statusno sensitive capability
  • get_core_uptimeno sensitive capability
  • get_encoder_countsno sensitive capability
  • get_firmware_versionno sensitive capability
  • get_ir_readingsno sensitive capability
  • get_mac_addressno sensitive capability
  • get_magnetometerno sensitive capability
  • get_motor_fault_stateno sensitive capability
  • get_motor_thermal_protection_statusno sensitive capability
  • get_processor_nameno sensitive capability
  • get_safety_statusno sensitive capability
  • get_sensor_datano sensitive capability
  • get_skuno sensitive capability
  • get_temperatureno sensitive capability
  • pivotno sensitive capability
  • reset_locatorno sensitive capability
  • reset_yawno sensitive capability
  • send_ir_messageno sensitive capability
  • set_all_ledsno sensitive capability
  • set_command_timeoutno sensitive capability
  • set_ledno sensitive capability
  • set_speed_limitno sensitive capability
  • start_ir_broadcastingno sensitive capability
  • start_ir_evadingno sensitive capability
  • start_ir_followingno sensitive capability
  • start_sensor_streamingno sensitive capability
  • stopno sensitive capability
  • stop_ir_broadcastingno sensitive capability
  • stop_ir_evadingno sensitive capability
  • stop_ir_followingno sensitive capability
  • stop_sensor_streamingno sensitive capability
  • test_immediate_returnno sensitive capability
  • test_slow_returnno sensitive capability
  • turn_leds_offno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.2.5 latest A 99/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/sphero-rvr-mcp/badge.svg)](https://mcptrustchecker.com/registry/sphero-rvr-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/sphero-rvr-mcp"><img src="https://mcptrustchecker.com/registry/sphero-rvr-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/sphero-rvr-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan sphero-rvr-mcp --online --registry pypi

Use the free API → How scoring works

More in Analytics & Monitoring