yahboom-mcp (sandraschi/yahboom-mcp) is an MCP server listed on the M8ven Trust Index. It scores 41 out of 100, grade D. It declares 13 tools. No publisher has claimed this listing.

D
Warning
41/100

yahboom-mcp

FastMCP 3.2 server plus Webapp for Yahboom Raspbot v2 robot car, ros2, raspberry pi

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

sandraschi

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Reads files from sensitive locations
Touches: ~/.ssh/id_rsa.pub
🔐
You'll be asked for 3 credentials: YAHBOOM_GEMINI_API_KEY, YAHBOOM_PASSWORD, TAPO_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes13 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

yahboom_tool

Unified control for Yahboom Raspbot v2 (ROS 2 Humble).

yahboom_demo

Boomy show-floor demos: floor chalk art, social talkbot, and the interaction demos (dog meeting + cafe host).

yahboom_agentic_workflow

Achieve a high-level robot goal by planning and executing a sequence of operations (SEP-1577). Uses sampling to let the LLM call get_robot_health, move_robot, and read_sensors as sub-tools.

yahboom_help_tool

Multi-level help system for the Yahboom MCP server. Supports drill-down: category (motion/sensors/connection/api/mcp_tools/startup/troubleshooting), then topic within each category.

ros_topic_list

List all active ROS 2 topics and their message types. Provides full visibility into the robot's sensory and control stack.

ros_node_info

Get detailed information about a specific ROS 2 node. Reveals publishers, subscribers, and services for the specified node.

ros_resync

Force a re-discovery of all ROS 2 topics and re-subscribe to sensors. Use this if telemetry (Battery, IMU) is missing while wheels still work.

ros_restart_bringup

Remotely restart the Yahboom bringup nodes via SSH. Use this as a 'Nuclear Option' if the robot is unresponsive or nodes are missing.

lidar

LIDAR and map data from Yahboom or Dreame D20 Pro.

yahboom_agent_mission

LLM mission planner: natural-language goal (e.g. \"find Benny\") → structured JSON plan (intent, behavior, target_description, optional nav2_goal, …). Same logic as POST /api/v1/agent/mission.

audio

Play/store/manage audio files through the USB voice module speaker.

query_logs

Query the in-memory log ring buffer for recent log entries.

yahboom_shutdown

Gracefully shut down the Yahboom MCP server process.

// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configYAHBOOM_IP
configYAHBOOM_FALLBACK_IP
configYAHBOOM_CONNECTION
configYAHBOOM_BRIDGE_PORT
configYAHBOOM_ESP32_PORT
configYAHBOOM_USE_MOCK_BRIDGE
configMCP_BRIDGE_URLS
configOLLAMA_BASE_URL
configLMSTUDIO_BASE_URL
configYAHBOOM_ROS2_CONTAINERTTL SSH/TCP probes, YAHBOOM_ROS2_CONTAINER, lifecycle (never started vs exited vs restart loop), optional docker logs preview (redacted).
configDREAME_MAP_URL
🔐 secretYAHBOOM_GEMINI_API_KEY
configYAHBOOM_GEMINI_MISSION_MODEL
configYAHBOOM_MISSION_TOPIC
configYAHBOOM_TAURI
configYAHBOOM_MCP_PORT
configYAHBOOM_MCP_HOST
configBOOMY_SENSOR_PORT
configBOOMY_SENSOR_BAUD
configDETECTION_CAM_URL
configYAHBOOM_USER
🔐 secretYAHBOOM_PASSWORD
configMCP_CENTRAL_DOCS
configYAHBOOM_BASE_URL
configOLLAMA_MODEL
configYAHBOOM_DRIVER_PROBE_SECS
configYAHBOOM_DOCKER_LOGS_TAIL
configYAHBOOM_DOCKER_LOGS_MAX_CHARS
configYAHBOOM_STACK_PROBE_SECS
configYAHBOOM_IMU_TOPIC
configYAHBOOM_ULTRASONIC_TOPIC
configYAHBOOM_LINE_TOPIC
configYAHBOOM_LINE_MSG_TYPE
configYAHBOOM_CAMERA_TOPIC
configYAHBOOM_CAMERA_DIRECT
configYAHBOOM_CAMERA_DEVICE
configYAHBOOM_DEMO_FAST
configYAHBOOM_DRAW_SPEED
configYAHBOOM_PEN_SERVO
configYAHBOOM_SPEECH_MCP_URL
configYAHBOOM_CAFE_FACTS
configYAHBOOM_TALKBOT_APPROACH
configYAHBOOM_TALKBOT_TURNS
configYAHBOOM_DISPLAY_CMD_PREFIX
configYAHBOOM_OLED_PAUSE_ROS
configTAPO_USER
🔐 secretTAPO_PASSWORD
configTAPO_IP
configYAHBOOM_VOICE_BAUD
configYAHBOOM_USB_AUDIO_DEV
configYAHBOOM_VOICE_DEVICE
configYAHBOOM_ESPEAK_VOICE
configYAHBOOM_ESPEAK_SPEED
configYAHBOOM_ESPEAK_PITCH
// quality suggestions

Tool annotations

7/13 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

13/13 tools missing one or more hints — yahboom_tool (missing: openWorldHint); yahboom_demo (missing: openWorldHint); yahboom_agentic_workflow (missing: openWorldHint), +10 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

5/13 tools referenced in tests (38%)

Write tests that reference each tool by name so every tool has at least one test.

No access to sensitive paths

Reads sensitive paths: ~/.ssh/id_rsa.pub

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/sandraschi/yahboom-mcp?variant=verified)](https://m8ven.ai/mcp/sandraschi/yahboom-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 4ac6718077b57449169df0a145e520c23cd1a149
code hash: d751cdad15e9e74f3bfddca689e1a6861a5cb85ef48b73b01cdf24f84628fa6d
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client