# ship.page (remote · ship.page)

Deploy HTML from any agent: POST markup, get a live URL. Static hosting API with MCP tools.

- Trust score: 81/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `ship.page`: 81/100 (this document), [markdown](https://verifymcp.io/servers/page-ship-ship-page/ship.md), [page](https://verifymcp.io/servers/page-ship-ship-page/ship)

## Channel facts

- Endpoint: `https://ship.page/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

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

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (deploy_html).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1586 tokens (~144/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the ship.page MCP server?

ship.page is a hosted endpoint at https://ship.page/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 page-ship-ship-page 'https://ship.page/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "page-ship-ship-page": {
      "url": "https://ship.page/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "page-ship-ship-page": {
      "type": "http",
      "url": "https://ship.page/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.page-ship-ship-page]
url = "https://ship.page/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add page-ship-ship-page --url 'https://ship.page/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  page-ship-ship-page:
    url: "https://ship.page/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "page-ship-ship-page": {
      "Transport": "http",
      "Url": "https://ship.page/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add page-ship-ship-page -t streamable-http -u 'https://ship.page/mcp'
```

### Other

```json
{
  "mcpServers": {
    "page-ship-ship-page": {
      "type": "http",
      "url": "https://ship.page/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-09-19 (score 81, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “deploy_html” rewrote its description, which is the text the model reads

### 2026-09-17 (score 81, +1)

- [security] Stability: 0.97 → pass
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “deploy_html” rewrote its description, which is the text the model reads

### 2026-09-15 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 77, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “remove_drop_password”, which the server declares destructive
- [security] New tool “set_drop_password”, which the server declares destructive
- [security] Tool “append_files” rewrote its description, which is the text the model reads
- [security] Tool “deploy_html” rewrote its description, which is the text the model reads
- [security] Tool “list_drops” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 1207 → 1586
- [cosmetic] “deploy_files” added an optional parameter “password”
- [cosmetic] “deploy_html” added an optional parameter “password”
- [cosmetic] “append_files” reworded the description of “slug”
- [cosmetic] “claim_drop” reworded the description of “slug”
- [cosmetic] “delete_drop” reworded the description of “slug”
- [cosmetic] “restore_drop” reworded the description of “slug”

### 2026-09-07 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 76, 0)

- [security] Tool “append_files” is now declared destructive
- [security] Tool “claim_drop” is now declared destructive
- [security] Tool “deploy_files” is now declared destructive
- [security] Tool “deploy_html” is now declared destructive

## MCP tools (11)

### `deploy_html` (~314 tokens)

Deploy a single HTML page

Deploy one HTML document and get back a live, unguessable https://<slug>.shipped.run/ URL. Anonymous: 10 deploys/min per IP, 10MB body cap, 30-day expiry. Pro ($4/mo): custom or no TTL, named drops.

Input parameters:

- `email` (string): Contact email for an anonymous deploy: the one-time claim link is mailed to it, so the drop stays recoverable even if the claim_token from the response is lost. Pass it whenever the deploy is for a h…
- `html` (string, required): The full HTML document to publish.
- `name` (string): Stable name for a redeployable drop (1-41 chars of [a-z0-9-]). Requires an active subscription; Team accounts serve it on their vanity subdomain.
- `password` (string): Shared password: 8-128 Unicode characters, at most 512 UTF-8 bytes. Requires active paid Pro/Team. Sent privately, never in the URL or response. Omit on a live named redeploy to preserve protection.…
- `ttl` (integer): Lifetime in seconds (min 60). Anonymous: max 2592000 (30 days), default 30 days. Signed-in free: max 7776000 (90 days), default 90 days. Paid: any value, omit for no expiry.

Output parameters:

- `claim_token` (string): One-time claim token (spc_...), present only on anonymous deploys and shown once. Anyone holding it can attach the drop to an account via claim_drop.
- `expires_at` (string|null): ISO timestamp, or null when the drop never expires
- `files` (array)
- `name` (string)
- `password_protected` (boolean)
- `plan` (string)
- `replaced` (boolean): Present with named deploys; true when an existing drop was replaced
- `slug` (string): Drop slug; the site is live at https://<slug>.shipped.run/
- `url` (string)

### `deploy_files` (~348 tokens)

Deploy a multi-file site

Deploy a map of path -> content as a multi-file site (must include index.html to serve at the root). Anonymous: up to 100 files per request, 30-day expiry (90 days once signed in). Pro ($4/mo): up to 900 files, custom or no TTL, named drops.

Input parameters:

- `email` (string): Contact email for an anonymous deploy: the one-time claim link is mailed to it, so the drop stays recoverable even if the claim_token from the response is lost. Pass it whenever the deploy is for a h…
- `files` (object, required): Map of relative paths (e.g. 'index.html', 'css/app.css') to either a string, or { encoding: 'base64', content } for binary files.
- `name` (string): Stable name for a redeployable drop (1-41 chars of [a-z0-9-]). Requires an active subscription; Team accounts serve it on their vanity subdomain.
- `password` (string): Shared password: 8-128 Unicode characters, at most 512 UTF-8 bytes. Requires active paid Pro/Team. Sent privately, never in the URL or response. Omit on a live named redeploy to preserve protection.…
- `ttl` (integer): Lifetime in seconds (min 60). Anonymous: max 2592000 (30 days), default 30 days. Signed-in free: max 7776000 (90 days), default 90 days. Paid: any value, omit for no expiry.

Output parameters:

- `claim_token` (string): One-time claim token (spc_...), present only on anonymous deploys and shown once. Anyone holding it can attach the drop to an account via claim_drop.
- `expires_at` (string|null): ISO timestamp, or null when the drop never expires
- `files` (array)
- `name` (string)
- `password_protected` (boolean)
- `plan` (string)
- `replaced` (boolean): Present with named deploys; true when an existing drop was replaced
- `slug` (string): Drop slug; the site is live at https://<slug>.shipped.run/
- `url` (string)

### `append_files` (~125 tokens)

Append files to an existing drop

Add files to a drop owned by the authenticated account (requires an sp_ API key and an active subscription): up to 900 files per call, 10,000 per drop total, and existing paths are overwritten. The drop keeps its current expiry and password protection.

Input parameters:

- `files` (object, required): Map of relative paths (e.g. 'index.html', 'css/app.css') to either a string, or { encoding: 'base64', content } for binary files.
- `slug` (string, required): The drop slug (the subdomain part of its ${domain} URL).

Output parameters:

- `expires_at` (string|null): ISO timestamp, or null when the drop never expires
- `files` (array): Paths added by this call
- `plan` (string)
- `slug` (string)
- `total_files` (integer): Total files on the drop after the append
- `url` (string)

### `list_drops` (~85 tokens)

List your drops

List drops owned by the authenticated account (requires an sp_ API key; anonymous drops are not listable). Returns slug, url, name, file counts, expiry and password_protected, newest first.

Input parameters:

- `limit` (integer): Max drops to return (1-500, default 100).
- `offset` (integer): Number of drops to skip (default 0).

Output parameters:

- `drops` (array)
- `total` (integer)

### `claim_drop` (~137 tokens)

Claim an anonymous drop

Attach an anonymously deployed drop to the authenticated account using its one-time claim token (spc_..., returned once by deploy_html/deploy_files). Claiming extends the drop to the free-account lifetime (90 days) and can revive an offline drop during its 30-day private recovery window. Claimed drops become listable, deletable, and — on paid plans — redeployable via named drops. Requires an sp_ API key.

Input parameters:

- `claim_token` (string, required): The one-time spc_... token returned at deploy time.
- `slug` (string, required): The drop slug (the subdomain part of its ${domain} URL).

Output parameters:

- `claimed` (boolean)
- `expires_at` (string|null): ISO timestamp after the claim's lifetime extension, or null
- `restored` (boolean): True when the drop had already expired and was revived by the claim
- `slug` (string)
- `url` (string)

### `restore_drop` (~92 tokens)

Restore an expired drop

Bring back an expired drop owned by the authenticated account while its files are still retained (requires an sp_ API key). Free accounts restore up to 30 days past expiry and the drop comes back at the 90-day lifetime; paid plans restore up to 90 days past expiry and the drop never expires again.

Input parameters:

- `slug` (string, required): The drop slug (the subdomain part of its ${domain} URL).

Output parameters:

- `expires_at` (string|null): ISO timestamp after the restore, or null when the drop never expires
- `restored` (boolean): False when the drop was not expired and nothing changed
- `slug` (string)
- `url` (string)

### `delete_drop` (~57 tokens)

Delete a drop

Permanently delete a drop owned by the authenticated account (requires an sp_ API key). The URL stops serving immediately and cannot be recovered.

Input parameters:

- `slug` (string, required): The drop slug (the subdomain part of its ${domain} URL).

Output parameters:

- `deleted` (string): Slug of the deleted drop

### `set_drop_password` (~149 tokens)

Set a drop password

Set or rotate the shared password on a drop you own. Requires an sp_ API key and active paid Pro/Team; unavailable billing returns an error, not a public drop. Visitors unlock in their browser. Never put the password in a URL.

Input parameters:

- `password` (string, required): Shared password: 8-128 Unicode characters, at most 512 UTF-8 bytes. Requires active paid Pro/Team. Sent privately, never in the URL or response. Omit on a live named redeploy to preserve protection.…
- `slug` (string, required): The drop slug (the subdomain part of its URL).

Output parameters:

- `password_protected` (boolean)
- `slug` (string)

### `remove_drop_password` (~61 tokens)

Remove a drop password

Remove password protection from a drop you own, making it readable by anyone with its URL. Requires an sp_ API key; works even after your paid subscription lapses.

Input parameters:

- `slug` (string, required): The drop slug (the subdomain part of its URL).

Output parameters:

- `password_protected` (boolean)
- `slug` (string)

### `get_limits` (~49 tokens)

Get plan limits

Show the ship.page plan matrix (anonymous free tier vs Pro $4/mo vs Team $19/mo) and, when an sp_ API key is present, the caller's current account/plan status.

Output parameters:

- `account` (object): Present when an sp_ API key was supplied
- `plans` (object): Plan matrix: anonymous, pro, team

### `get_account` (~40 tokens)

Get account info

Show the authenticated account's plan, subscription status and usage (requires an sp_ API key). Anonymous callers should use get_limits for the static free-tier limits.

Output parameters:

- `accountId` (string)
- `activeSubscription` (boolean)
- `cancelAt` (string|null)
- `currentPeriodEnd` (string|null)
- `plan` (string): free | pro | team
- `portalAvailable` (boolean)

## Diagnostics

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

## Score history

- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 81
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 77
- 2026-09-09: 77
- 2026-09-08: 77
- 2026-09-07: 77
- 2026-09-06: 76
- 2026-09-05: 76
- 2026-09-04: 75
- 2026-09-03: 75
- 2026-09-02: 74
- 2026-09-01: 74
- 2026-08-31: 73
- 2026-08-30: 73
- 2026-08-29: 72
- 2026-08-28: 72
- 2026-08-27: 72
- 2026-08-26: 71
- 2026-08-25: 70
- 2026-08-24: 69
- 2026-08-23: 68
- 2026-08-22: 68

## Common questions

### What is the ship.page MCP server?

ship.page is an MCP server listed in the public MCP registry as page.ship/ship-page. Deploy HTML from any agent: POST markup, get a live URL. Static hosting API with MCP tools. This page covers its hosted endpoint (https://ship.page/mcp).

### Is the ship.page MCP server safe to use?

ship.page scores 81 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 ship.page MCP server expose?

ship.page exposes 11 tools: deploy_html, deploy_files, append_files, list_drops, claim_drop, and 6 more. Their descriptions and schemas cost roughly 1,457 tokens of context every time the server is loaded.

### Does the ship.page MCP server require authentication?

No. We connected to ship.page without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ship.page MCP server still maintained?

ship.page is still listed as active in the MCP registry. We last reached this channel on 20 September 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://ship.page/mcp
- Repository: https://github.com/bitgate/ship.page
- Website: https://ship.page/
- Changelog RSS feed: https://verifymcp.io/servers/page-ship-ship-page/ship.xml
- Changelog JSON feed: https://verifymcp.io/servers/page-ship-ship-page/ship.json
- HTML version of this page: https://verifymcp.io/servers/page-ship-ship-page/ship