Shipvo
REMOTE · SIM.SHIPVO.DEV · 2 COMPONENTS
Open a React Native app in a simulated phone: read the screen, tap, type, set device state.
Available components
Last scanned (19 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Browser Automation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1086 tokens (~60/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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 67
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 4 Nov 2026 · Probed https://sim.shipvo.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shipvo.dev | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d6c75b7df6ac10760e6db137007e7da3 |
| SANs: shipvo.dev, sim.shipvo.dev, *.sim.shipvo.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sim.shipvo.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| shipvo.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sim.shipvo.dev/mcp | Verified | 200 | |
| http (plaintext) | http://sim.shipvo.dev/mcp | Inconclusive | 401 |
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 is a hosted endpoint at https://sim.shipvo.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · sim.shipvo.dev
claude mcp add --transport http shipvo-shipvo 'https://sim.shipvo.dev/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 hosted endpoint (https://sim.shipvo.dev/mcp).
Is the Shipvo MCP server safe to use?
Shipvo scores 68 out of 100 on VerifyMCP. 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.
Does the Shipvo MCP server require authentication?
Yes. Shipvo asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Shipvo MCP server still maintained?
Shipvo is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.