Control a real Chrome browser to complete any task: fill forms, extract data, book flights.
Shipvo 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.
What it does
Open a React Native app in a simulated phone: read the screen, tap, type, set device state.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user shipvo-mcp '--' npx -y @shipvo/mcp
# 2 — ask your agent for something these tools do
# list_apps, open_app, list_sessions and 15 more
Remote: no sign-in · Package: API key.
Shipvo costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
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 shipvo-mcp '--' npx -y @shipvo/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Its publisher also runs it at https://sim.shipvo.dev/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http shipvo-mcp https://sim.shipvo.dev/mcpOne 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.
18 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.
Apps this server can open, with what each one does. Optional query filters by name, description or category (e.g. 'shop', 'douala').
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | — |
Open an app in a fresh phone-sized session and return its first screen.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | App id from list_apps, optionally with a release: 'tide' (local build), 'tide@latest' or 'tide@r13' (the published release phones run) |
| session | string | no | Session name (default: generated). One session is one phone. |
| seed_cart | array | no | Start with these items already in the cart (test shortcut). Each line: { product_id, quantity }; { id, qty } also works. |
| dark | boolean | no | Dark mode |
Open simulator sessions (phones) on this server: id, app, release and when each started. Use to resume after a reconnect.
No parameter schema on file.
The current screen as an accessibility tree with refs.
No parameter schema on file.
Tap a button, link or choice by ref. Returns the new screen.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | yes | — | |
| ref | string | yes | Element ref from the screen, e.g. e42 |
Scroll the page (down/up) or a horizontal rail (right/left, give the rail's ref). Returns the new screen.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | yes | — | |
| direction | string | yes | — |
| ref | string | no | Scroll inside this element (a rail or list); omit for the page |
Go back one screen.
No parameter schema on file.
A PNG of the phone screen (for checking layout, colours, images). The tree from screen is usually enough to act.
No parameter schema on file.
Change what the simulated phone has: location, a barcode in front of the camera, permission states, whether the fingerprint will match, whether a payment will be approved, network on/off. Takes effect for the next action.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | yes | — | |
| location | object | no | — |
| camera | object | no | — |
| permissions | object | no | — |
| biometrics | object | no | — |
| payment | object | no | — |
| online | boolean | no | — |
Deliver a push notification to the simulated phone; it appears as a banner the agent can tap.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | yes | — | |
| title | string | yes | — |
| body | string | yes | — |
| data | object | no | — |
The notification shade: notifications delivered to the simulated phone in this session (their banners vanish after 5 s, like a heads-up on a real phone).
No parameter schema on file.
Tap a notification from the shade (newest if no id is given): the app handles it exactly as if its banner was tapped.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | yes | — | |
| id | string | no | — |
What the app did with the device in this session: permission prompts and answers, location reads, scans, fingerprint checks, payments, notifications, shares.
No parameter schema on file.
Put the simulated phone back to a known state (permissions undetermined, default location, nothing in front of the camera, log cleared), optionally with a new profile.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | yes | — | |
| platform | string | no | — |
| api | number | no | — |
Close the session and get a report: steps taken, and the orders the app sent to its backend during the session.
No parameter schema on file.
List the owner commands of an app (content, prices, offers, orders, publish). Needs PN_OWNER_TOKEN.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | — |
Run an owner command against the live app (changes are audited; publish makes them live on every phone within seconds).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | — |
| command | string | yes | — |
| args | object | no | — |
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- 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 Shipvo or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tools were statically extracted from the published source (18 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 |
|---|---|---|
| list_apps | no tags | |
| open_app | external-sink | external-sink: handler sends an HTTP POST (fetch(SIM + path) at dist/server.js:38 |
| list_sessions | no tags | |
| screen | external-sink | external-sink: handler sends an HTTP POST (fetch(SIM + path) at dist/server.js:38 |
| tap | external-sink | external-sink: handler sends an HTTP POST (fetch(SIM + path) at dist/server.js:38 |
| type | external-sink | external-sink: handler sends an HTTP POST (fetch(SIM + path) at dist/server.js:38 |
| scroll | external-sink | external-sink: handler sends an HTTP POST (fetch(SIM + path) at dist/server.js:38 |
| back | external-sink | external-sink: handler sends an HTTP POST (fetch(SIM + path) at dist/server.js:38 |
| screenshot | external-sink | external-sink: handler sends an HTTP POST (fetch(SIM + path) at dist/server.js:38 |
| set_device | external-sink | external-sink: handler sends an HTTP POST (fetch(SIM + path) at dist/server.js:38 |
| push_notification | external-sink | external-sink: handler sends an HTTP POST (fetch(SIM + path) at dist/server.js:38 |
| notifications | external-sink | external-sink: handler sends an HTTP POST (fetch(SIM + path) at dist/server.js:38 |
| open_notification | external-sink | external-sink: handler sends an HTTP POST (fetch(SIM + path) at dist/server.js:38 |
| device_log | external-sink | external-sink: handler sends an HTTP POST (fetch(SIM + path) at dist/server.js:38 |
| device_reset | external-sink | external-sink: handler sends an HTTP POST (fetch(SIM + path) at dist/server.js:38 |
| end_session | no tags | |
| owner_describe | no tags | |
| owner_command | code-execexternal-sink | code-exec: parameter "command"; external-sink: handler sends an HTTP POST (fetch(${CONTROL}/app/${app}/api/command) at dist/server.js:152 |
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
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 0.0.7. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
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.
Any signed-in account that does not publish Shipvo can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.