MCP server for interacting with the Scryfall MTG API
Nothing to run from here
AI Rover Studio is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
12
downloads a day
local
runs on your machine
712
downloads in 30d
What it does
Let an AI agent drive a 2D robot rover simulator in the browser: sensors, camera, wiring and code.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user ai-rover-studio-mcp '--' npx -y ai-rover-mcp
# 2 — ask your agent for something these tools do
# open_simulator, connection_status, capture_camera and 38 more
AI Rover Studio costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TAAll 1 server
taewankung1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts AI Rover Studio as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user ai-rover-studio-mcp '--' npx -y ai-rover-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take ROVER_SIMULATOR_URL (Simulator page that open_simulator opens: a URL or a path to a local build. Default: https://ai-rover.app/app/?mcp=on), ROVER_BRIDGE_PORT (Local WebSocket port the simulator page connects to. Default: 8765), ROVER_ALLOWED_ORIGINS (Extra comma-separated https origins the bridge accepts) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
41 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Open the AI Rover Studio page in the default browser and wait (up to 15 s) for it to connect to this MCP server.
No parameter schema on file.
Report whether the simulator page is connected to this MCP server.
No parameter schema on file.
Take a picture with the rover's forward-facing camera (needs the camera module). Returns a 320×240 first-person PNG
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fov_deg | number | no | Change the horizontal field of view first (default 60°) |
Current robot pose (x, y, heading_deg), velocity, every enabled sensor reading, face display state, plus simulation status (running, autopilot, power, lamp position).
No parameter schema on file.
Fresh readings from all enabled sensors, with their mounting position, angle, range and unit.
No parameter schema on file.
Move the rover for a fixed time: forward / backward, or turn left / right in place. Turns autopilot off and starts the simulation.
No parameter schema on file.
Turn the rover in place by an exact angle (+ = right / clockwise, − = left) at ≈115°/s, then return the observation.
No parameter schema on file.
Run JavaScript on the robot with the rover library (same as the Code page; it replaces any running program and starts the simulation).
No parameter schema on file.
Stop the running rover program (its worker is terminated, the wheels stop).
No parameter schema on file.
The current/last rover program: code, status (idle, running, listening, done, stopped, error), error { message, line } and the last 50 console lines.
No parameter schema on file.
Emergency stop: cancel any movement, turn autopilot off and pause the simulation.
No parameter schema on file.
Start (running=true) or pause (running=false) the physics simulation.
No parameter schema on file.
Enable the built-in rule-based autopilot (seeks the light, backs away from obstacles; also starts the simulation) or disable it.
No parameter schema on file.
Set motor power in percent (10–100). Max speed is 170 px/s at 100 % (drive uses 65 % of it forward, 55 % backward).
No parameter schema on file.
Show an expression on the robot's face display (emulated SSD1306 128×64 OLED); the message appears in the top text line and scrolls if long.
No parameter schema on file.
Make the rover "say" a text on the Face Display module (128×64 OLED): a small rover face with a talking mouth
No parameter schema on file.
Fit a different Face Display module: "ssd1306" (0.96" 128×64 monochrome OLED, I²C; default),
No parameter schema on file.
Show a picture on the Face Display module for seconds, then return to the face.
No parameter schema on file.
Read back what the Face Display module is showing: mode (face/text), text lines, module stats (frames, fps, bytes)
No parameter schema on file.
Move the light source to world coordinates (clamped to 42–758 × 42–478).
No parameter schema on file.
Put the rover back at its start pose (120, 265, heading 0°) and the light at (690, 70). Turns autopilot off.
No parameter schema on file.
Send a message to the in-page Agent Chat (offline Thai/English command parser, e.g. "ไปหาแสง", "อ่านเซนเซอร์", "เดินหน้า 2 วินาที") and return the rover's reply. It shows up in the chat panel.
No parameter schema on file.
The Robot Capability Manifest (ai-cartridge/body-v1): motors, installed sensor modules and display.
No parameter schema on file.
All configured sensors (enabled or not) with id, type, mounting position, angle and range.
No parameter schema on file.
Install a new sensor on the rover body. Unspecified fields use the type defaults (centre of the body, facing forward).
No parameter schema on file.
Change a sensor's name, type, mounting position, angle, range or enabled flag. Use list_sensors to find ids.
No parameter schema on file.
Uninstall a sensor by id.
No parameter schema on file.
Install or remove a body module: "wheels" (drive motors + wheels; without them the rover cannot move),
No parameter schema on file.
Control the Head module (pan servo, needs set_module head first). angle_deg turns the face to −90…90° relative to the body
No parameter schema on file.
Press a push-button module (a sensor of type "button") for seconds and release it, like a person would.
No parameter schema on file.
Button presses since the last call (oldest first, then cleared): { id, name, press: "short" | "long", seconds, at (ms epoch) },
No parameter schema on file.
Head module status: angle_deg, target_deg, mode (manual / track_light), tracking phase and the head light brightness.
No parameter schema on file.
The map the rover has built from its own sensors only (not the true layout): an occupancy grid of 10 px cells
No parameter schema on file.
How the fitted rover body wires to a real microcontroller (the Wiring page): for each part (TB6612FNG motor driver,
No parameter schema on file.
Bill of materials for building the fitted rover body for real (the parts tab on the Wiring page):
No parameter schema on file.
A complete program for the real robot, generated from the fitted body and the wiring pin map: an Arduino sketch
No parameter schema on file.
World size, light position, all obstacles (id, kind, shape, position, size, color) and colored floor tapes.
No parameter schema on file.
Place an object in the world to test sensors, collisions or the camera. Kinds: cylinder / ball (circle, radius r),
No parameter schema on file.
Remove an obstacle by id (see list_world).
No parameter schema on file.
Stick a strip of colored tape on the floor (for the color sensor, line following and the camera).
No parameter schema on file.
Remove a floor tape by id (see list_world).
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install AI Rover Studio or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 1.1.2 · scanned 1 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings1 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digest572875aec3ce781d4b1c2cb85623dc712e5b538a9f3f15d46663b559f8b7b76c
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (41 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| open_simulator | state-write | state-write: declares readOnlyHint: false |
| connection_status | no tags | |
| capture_camera | no tags | |
| get_observation | no tags | |
| read_sensors | no tags | |
| drive | state-write | state-write: declares readOnlyHint: false |
| turn | state-write | state-write: declares readOnlyHint: false |
| run_program | state-write | state-write: declares readOnlyHint: false |
| stop_program | state-write | state-write: declares readOnlyHint: false |
| get_program | no tags | |
| stop | state-write | state-write: declares readOnlyHint: false |
| set_simulation | no tags | |
| set_autopilot | no tags | |
| set_power | no tags | |
| set_emotion | no tags | |
| display_text | no tags | |
| set_display | no tags | |
| draw_display | no tags | |
| read_display | no tags | |
| move_light | no tags | |
| reset_world | no tags | |
| send_chat | no tags | |
| get_manifest | no tags | |
| list_sensors | no tags | |
| add_sensor | no tags | |
| update_sensor | no tags | |
| remove_sensor | state-write | state-write: declares destructiveHint: true |
| set_module | no tags | |
| set_head | state-write | state-write: declares readOnlyHint: false |
| press_button | state-write | state-write: declares readOnlyHint: false |
| get_button_events | state-write | state-write: declares readOnlyHint: false |
| get_head | no tags | |
| get_sensor_map | state-write | state-write: declares readOnlyHint: false |
| get_wiring | state-write | state-write: declares readOnlyHint: false |
| get_bom | state-write | state-write: declares readOnlyHint: false |
| get_firmware | state-write | state-write: declares readOnlyHint: false |
| list_world | no tags | |
| add_obstacle | no tags | |
| remove_obstacle | state-write | state-write: declares destructiveHint: true |
| add_color_tape | no tags | |
| remove_color_tape | state-write | state-write: declares destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest572875aec3ce781d
Scanned2026-11-01
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.1.2. Pin a release below and the command asks for exactly that one.
1.1.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish AI Rover Studio can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.