# Shipvo (remote · sim.shipvo.dev)

Open a React Native app in a simulated phone: read the screen, tap, type, set device state.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `sim.shipvo.dev`: 68/100 (this document), [markdown](https://verifymcp.io/servers/shipvo-shipvo/sim.md), [page](https://verifymcp.io/servers/shipvo-shipvo/sim)
- npm · `@shipvo/mcp`: 73/100, [markdown](https://verifymcp.io/servers/shipvo-shipvo/shipvo-mcp.md), [page](https://verifymcp.io/servers/shipvo-shipvo/shipvo-mcp)

## Channel facts

- Endpoint: `https://sim.shipvo.dev/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `0.0.6`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1086 tokens (~60/item across 18 items; 18 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 53% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http shipvo-shipvo 'https://sim.shipvo.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "shipvo-shipvo": {
      "url": "https://sim.shipvo.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "shipvo-shipvo": {
      "type": "http",
      "url": "https://sim.shipvo.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.shipvo-shipvo]
url = "https://sim.shipvo.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shipvo-shipvo": {
      "type": "remote",
      "url": "https://sim.shipvo.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shipvo-shipvo --url 'https://sim.shipvo.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  shipvo-shipvo:
    url: "https://sim.shipvo.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "shipvo-shipvo": {
      "Transport": "http",
      "Url": "https://sim.shipvo.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add shipvo-shipvo -t streamable-http -u 'https://sim.shipvo.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "shipvo-shipvo": {
      "type": "http",
      "url": "https://sim.shipvo.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-02 (score 68, +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.

### 2026-11-01 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 67)

First indexed and scored.

## MCP tools (18)

### `list_apps` (~47 tokens)

Apps this server can open, with what each one does. Optional query filters by name, description or category (e.g. 'shop', 'douala').

Input parameters:

- `query` (string)

### `open_app` (~133 tokens)

Open an app in a fresh phone-sized session and return its first screen.

Input parameters:

- `app` (string, required): 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.

### `list_sessions` (~35 tokens)

Open simulator sessions (phones) on this server: id, app, release and when each started. Use to resume after a reconnect.

### `screen` (~28 tokens)

The current screen as an accessibility tree with refs.

Input parameters:

- `session` (string, required): Session from open_app

### `tap` (~51 tokens)

Tap a button, link or choice by ref. Returns the new screen.

Input parameters:

- `ref` (string, required): Element ref from the screen, e.g. e42
- `session` (string, required): Session from open_app

### `type` (~71 tokens)

Type into a text field by ref (replaces its content). Returns the new screen.

Input parameters:

- `enter` (boolean): Press Enter afterwards
- `ref` (string, required): Element ref from the screen, e.g. e42
- `session` (string, required): Session from open_app
- `text` (string, required)

### `scroll` (~73 tokens)

Scroll the page (down/up) or a horizontal rail (right/left, give the rail's ref). Returns the new screen.

Input parameters:

- `direction` (string, required)
- `ref` (string): Scroll inside this element (a rail or list); omit for the page
- `session` (string, required): Session from open_app

### `back` (~23 tokens)

Go back one screen.

Input parameters:

- `session` (string, required): Session from open_app

### `screenshot` (~45 tokens)

A PNG of the phone screen (for checking layout, colours, images). The tree from `screen` is usually enough to act.

Input parameters:

- `session` (string, required): Session from open_app

### `set_device` (~106 tokens)

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.

Input parameters:

- `biometrics` (object)
- `camera` (object)
- `location` (object)
- `online` (boolean)
- `payment` (object)
- `permissions` (object)
- `session` (string, required): Session from open_app

### `push_notification` (~59 tokens)

Deliver a push notification to the simulated phone; it appears as a banner the agent can tap.

Input parameters:

- `body` (string, required)
- `data` (object)
- `session` (string, required): Session from open_app
- `title` (string, required)

### `notifications` (~49 tokens)

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).

Input parameters:

- `session` (string, required): Session from open_app

### `open_notification` (~53 tokens)

Tap a notification from the shade (newest if no id is given): the app handles it exactly as if its banner was tapped.

Input parameters:

- `id` (string)
- `session` (string, required): Session from open_app

### `device_log` (~49 tokens)

What the app did with the device in this session: permission prompts and answers, location reads, scans, fingerprint checks, payments, notifications, shares.

Input parameters:

- `session` (string, required): Session from open_app

### `device_reset` (~66 tokens)

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.

Input parameters:

- `api` (number)
- `platform` (string)
- `session` (string, required): Session from open_app

### `end_session` (~43 tokens)

Close the session and get a report: steps taken, and the orders the app sent to its backend during the session.

Input parameters:

- `session` (string, required): Session from open_app

### `owner_describe` (~39 tokens)

List the owner commands of an app (content, prices, offers, orders, publish). Needs PN_OWNER_TOKEN.

Input parameters:

- `app` (string, required)

### `owner_command` (~54 tokens)

Run an owner command against the live app (changes are audited; `publish` makes them live on every phone within seconds).

Input parameters:

- `app` (string, required)
- `args` (object)
- `command` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/shipvo-shipvo/sim#diagnostics

## Score history

- 2026-11-04: 68
- 2026-11-03: 68
- 2026-11-02: 68
- 2026-11-01: 67
- 2026-10-31: 67

## Common questions

### 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.

## Links

- Remote endpoint: https://sim.shipvo.dev/mcp
- Authorisation metadata: https://sim.shipvo.dev/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/shipvo/shipvo
- Website: https://shipvo.dev/
- Changelog RSS feed: https://verifymcp.io/servers/shipvo-shipvo/sim.xml
- Changelog JSON feed: https://verifymcp.io/servers/shipvo-shipvo/sim.json
- HTML version of this page: https://verifymcp.io/servers/shipvo-shipvo/sim