ship.page
REMOTE · SHIP.PAGE · SCANNED SEP 20
Deploy HTML from any agent: POST markup, get a live URL. Static hosting API with MCP tools.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (deploy_html). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability75
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · ship.page
claude mcp add --transport http page-ship-ship-page 'https://ship.page/mcp'
{
"mcpServers": {
"page-ship-ship-page": {
"url": "https://ship.page/mcp"
}
}
} {
"servers": {
"page-ship-ship-page": {
"type": "http",
"url": "https://ship.page/mcp"
}
}
} [mcp_servers.page-ship-ship-page] url = "https://ship.page/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"page-ship-ship-page": {
"type": "remote",
"url": "https://ship.page/mcp",
"enabled": true
}
}
} openclaw mcp add page-ship-ship-page --url 'https://ship.page/mcp' --transport streamable-http
mcp_servers:
page-ship-ship-page:
url: "https://ship.page/mcp" {
"McpServers": {
"page-ship-ship-page": {
"Transport": "http",
"Url": "https://ship.page/mcp"
}
}
} assistant mcp add page-ship-ship-page -t streamable-http -u 'https://ship.page/mcp'
{
"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.
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.
- 19 Sept 26 0
- 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 security
- 17 Sept 26 +1
- 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 security
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 10 Sept 26 0
- 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 security
- Schema quality: 1207 → 1586 ▼ functional
- “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” cosmetic
- 7 Sept 26 +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.
- 6 Sept 26 0
- 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 security
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 20 Sept 2026 · Probed https://ship.page/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ship.page | CN=WE1,O=Google Trust Services,C=US | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | d8e63e062e0987113641458ac791fb7 |
| SANs: ship.page, *.ship.page | ||||||
| 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 ship.page. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| page. | present | 64712 | 8 | Verified |
| ship.page. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ship.page/mcp | Verified | 200 | |
| http (plaintext) | http://ship.page/mcp | HTTPS enforced | 301 | https://ship.page/mcp |
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 →
append_files Append files to an existing drop ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| files | object | yes | Map of relative paths (e.g. 'index.html', 'css/app.css') to either a string, or { encoding: 'base64', content } for binary files. |
| slug | string | yes | The drop slug (the subdomain part of its ${domain} URL). |
| Name | Type | Req | Description |
|---|---|---|---|
| expires_at | string|null | yes | ISO timestamp, or null when the drop never expires |
| files | array | yes | Paths added by this call |
| plan | string | – | – |
| slug | string | yes | – |
| total_files | integer | yes | Total files on the drop after the append |
| url | string | yes | – |
No examples provided.
claim_drop Claim an anonymous drop ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_token | string | yes | The one-time spc_... token returned at deploy time. |
| slug | string | yes | The drop slug (the subdomain part of its ${domain} URL). |
| Name | Type | Req | Description |
|---|---|---|---|
| claimed | boolean | yes | – |
| 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 | yes | – |
| url | string | yes | – |
No examples provided.
delete_drop Delete a drop ~57
Permanently delete a drop owned by the authenticated account (requires an sp_ API key). The URL stops serving immediately and cannot be recovered.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The drop slug (the subdomain part of its ${domain} URL). |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | string | yes | Slug of the deleted drop |
No examples provided.
deploy_files Deploy a multi-file site ~348
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | ISO timestamp, or null when the drop never expires |
| files | array | yes | – |
| name | string | – | – |
| password_protected | boolean | yes | – |
| plan | string | yes | – |
| replaced | boolean | – | Present with named deploys; true when an existing drop was replaced |
| slug | string | yes | Drop slug; the site is live at https://<slug>.shipped.run/ |
| url | string | yes | – |
No examples provided.
deploy_html Deploy a single HTML page ~314
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | ISO timestamp, or null when the drop never expires |
| files | array | yes | – |
| name | string | – | – |
| password_protected | boolean | yes | – |
| plan | string | yes | – |
| replaced | boolean | – | Present with named deploys; true when an existing drop was replaced |
| slug | string | yes | Drop slug; the site is live at https://<slug>.shipped.run/ |
| url | string | yes | – |
No examples provided.
get_account Get account info ~40
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | – |
| activeSubscription | boolean | yes | – |
| cancelAt | string|null | – | – |
| currentPeriodEnd | string|null | – | – |
| plan | string | yes | free | pro | team |
| portalAvailable | boolean | – | – |
No examples provided.
get_limits Get plan limits ~49
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| account | object | – | Present when an sp_ API key was supplied |
| plans | object | yes | Plan matrix: anonymous, pro, team |
No examples provided.
list_drops List your drops ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max drops to return (1-500, default 100). |
| offset | integer | – | Number of drops to skip (default 0). |
| Name | Type | Req | Description |
|---|---|---|---|
| drops | array | yes | – |
| total | integer | yes | – |
No examples provided.
remove_drop_password Remove a drop password ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The drop slug (the subdomain part of its URL). |
| Name | Type | Req | Description |
|---|---|---|---|
| password_protected | boolean | yes | – |
| slug | string | yes | – |
No examples provided.
restore_drop Restore an expired drop ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The drop slug (the subdomain part of its ${domain} URL). |
| Name | Type | Req | Description |
|---|---|---|---|
| expires_at | string|null | yes | ISO timestamp after the restore, or null when the drop never expires |
| restored | boolean | yes | False when the drop was not expired and nothing changed |
| slug | string | yes | – |
| url | string | yes | – |
No examples provided.
set_drop_password Set a drop password ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| password | string | yes | 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 | yes | The drop slug (the subdomain part of its URL). |
| Name | Type | Req | Description |
|---|---|---|---|
| password_protected | boolean | yes | – |
| slug | string | yes | – |
No examples provided.
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.