Shipvo
NPM · @SHIPVO/MCP · 2 COMPONENTS
Open a React Native app in a simulated phone: read the screen, tap, type, set device state.
Available components
Last scanned (1 hour ago)
Scores higher than 45% of npm servers
Category Browser Automation
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to shipvo/shipvo). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1260 tokens (~70/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 53% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 58
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@shipvo/mcp@0.0.6
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | shipvo/shipvo |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/shipvo/shipvo/.github/workflows/publish-npm.yml@refs/heads/main |
| Rekor log index | 3614764297 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b8ce6ccd2e03284c17648152b0300300733c3aa855e6cb8f9b5e60586c3e567dd84c6488aef673f629d1a37675fe425e3f73f9f074969656543abce2f |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
back ~23
Go back one screen.
| Name | Type | Req | Description |
|---|---|---|---|
| session | string | yes | Session from open_app |
No output schema declared.
No examples provided.
device_log ~49
What the app did with the device in this session: permission prompts and answers, location reads, scans, fingerprint checks, payments, notifications, shares.
| Name | Type | Req | Description |
|---|---|---|---|
| session | string | yes | Session from open_app |
No output schema declared.
No examples provided.
device_reset ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api | number | – | – |
| platform | string | – | – |
| session | string | yes | Session from open_app |
No output schema declared.
No examples provided.
end_session ~43
Close the session and get a report: steps taken, and the orders the app sent to its backend during the session.
| Name | Type | Req | Description |
|---|---|---|---|
| session | string | yes | Session from open_app |
No output schema declared.
No examples provided.
list_apps ~47
Apps this server can open, with what each one does. Optional query filters by name, description or category (e.g. 'shop', 'douala').
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | – |
No output schema declared.
No examples provided.
list_sessions ~35
Open simulator sessions (phones) on this server: id, app, release and when each started. Use to resume after a reconnect.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
notifications ~49
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).
| Name | Type | Req | Description |
|---|---|---|---|
| session | string | yes | Session from open_app |
No output schema declared.
No examples provided.
open_app ~133
Open an app in a fresh phone-sized session and return its first screen.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
| dark | boolean | – | Dark mode |
| seed_cart | array | – | Start with these items already in the cart (test shortcut). Each line: { product_id, quantity }; { id, qty } also works. |
| session | string | – | Session name (default: generated). One session is one phone. |
No output schema declared.
No examples provided.
open_notification ~53
Tap a notification from the shade (newest if no id is given): the app handles it exactly as if its banner was tapped.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | – |
| session | string | yes | Session from open_app |
No output schema declared.
No examples provided.
owner_command ~54
Run an owner command against the live app (changes are audited; `publish` makes them live on every phone within seconds).
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | – |
| args | object | – | – |
| command | string | yes | – |
No output schema declared.
No examples provided.
owner_describe ~39
List the owner commands of an app (content, prices, offers, orders, publish). Needs PN_OWNER_TOKEN.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | – |
No output schema declared.
No examples provided.
push_notification ~59
Deliver a push notification to the simulated phone; it appears as a banner the agent can tap.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| data | object | – | – |
| session | string | yes | Session from open_app |
| title | string | yes | – |
No output schema declared.
No examples provided.
screen ~28
The current screen as an accessibility tree with refs.
| Name | Type | Req | Description |
|---|---|---|---|
| session | string | yes | Session from open_app |
No output schema declared.
No examples provided.
screenshot ~45
A PNG of the phone screen (for checking layout, colours, images). The tree from `screen` is usually enough to act.
| Name | Type | Req | Description |
|---|---|---|---|
| session | string | yes | Session from open_app |
No output schema declared.
No examples provided.
scroll ~73
Scroll the page (down/up) or a horizontal rail (right/left, give the rail's ref). Returns the new screen.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | yes | – |
| ref | string | – | Scroll inside this element (a rail or list); omit for the page |
| session | string | yes | Session from open_app |
No output schema declared.
No examples provided.
set_device ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| biometrics | object | – | – |
| camera | object | – | – |
| location | object | – | – |
| online | boolean | – | – |
| payment | object | – | – |
| permissions | object | – | – |
| session | string | yes | Session from open_app |
No output schema declared.
No examples provided.
tap ~51
Tap a button, link or choice by ref. Returns the new screen.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | yes | Element ref from the screen, e.g. e42 |
| session | string | yes | Session from open_app |
No output schema declared.
No examples provided.
type ~71
Type into a text field by ref (replaces its content). Returns the new screen.
| Name | Type | Req | Description |
|---|---|---|---|
| enter | boolean | – | Press Enter afterwards |
| ref | string | yes | Element ref from the screen, e.g. e42 |
| session | string | yes | Session from open_app |
| text | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Shipvo MCP server?
Shipvo runs locally as an npm package, launched with npx -y @shipvo/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @shipvo/mcp
claude mcp add shipvo-shipvo -- npx -y @shipvo/mcp
What is the Shipvo MCP server?
Shipvo is an MCP server listed in the public MCP registry as io.github.shipvo/shipvo. Open a React Native app in a simulated phone: read the screen, tap, type, set device state. This page covers its npm package (@shipvo/mcp).
Is the Shipvo MCP server safe to use?
Shipvo scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Shipvo MCP server expose?
Shipvo exposes 18 tools: list_apps, open_app, list_sessions, screen, tap, and 13 more. Their descriptions and schemas cost roughly 1,024 tokens of context every time the server is loaded.
Is the Shipvo MCP server still maintained?
Shipvo is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Shipvo MCP server under?
Shipvo declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.