ship.page

Deploy a multi-file site

deploy_files

Destructive

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 Schema

TableJSON Schema

Name	Required	Description
`ttl`	No	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`	No	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.
`agent`	No	Name of the AI agent or app publishing this drop, e.g. 'chatgpt', 'claude', 'cursor'. AI agents: always set this.
`email`	No	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 human. Ignored for authenticated deploys (those are owned already).
`files`	Yes	Map of relative paths (e.g. 'index.html', 'css/app.css') to either a string, or { encoding: 'base64', content } for binary files.
`password`	No	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. Recreating an expired or purged name is a new drop: send the password again.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes
`name`	No
`plan`	Yes
`slug`	Yes	Drop slug; the site is live at https://<slug>.shipped.run/
`files`	Yes
`replaced`	No	Present with named deploys; true when an existing drop was replaced
`expires_at`	Yes	ISO timestamp, or null when the drop never expires
`claim_token`	No	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.
`password_protected`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / agent

Added value: +{
+  "description": "Name of the AI agent or app publishing this drop, e.g. 'chatgpt', 'claude', 'cursor'. AI agents: always set this.",
+  "maxLength": 64,
+  "type": "string"
+}

Changed1 schema field changedSep 18, 2026

changedOutput schema / properties / slug / description

Previous value: -"Drop slug; the site is live at https://<slug>.shipped.cloud/"New value: +"Drop slug; the site is live at https://<slug>.shipped.run/"

Changed1 schema field changedSep 16, 2026

changedOutput schema / properties / slug / description

Previous value: -"Drop slug; the site is live at https://<slug>.shipped.run/"New value: +"Drop slug; the site is live at https://<slug>.shipped.cloud/"

Changed1 schema field changedSep 16, 2026

changedOutput schema / properties / slug / description

Previous value: -"Drop slug; the site is live at https://<slug>.shipped.page/"New value: +"Drop slug; the site is live at https://<slug>.shipped.run/"

Changed1 schema field changedSep 10, 2026

changedOutput schema / properties / slug / description

Previous value: -"Drop slug; the site is live at https://<slug>.shipped.run/"New value: +"Drop slug; the site is live at https://<slug>.shipped.page/"

Changed3 schema fields changedSep 9, 2026

addedInput schema / properties / password

Added value: +{
+  "description": "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. Recreating an expired or purged name is a new drop: send the password again.",
+  "maxLength": 128,
+  "minLength": 8,
+  "type": "string",
+  "writeOnly": true
+}

addedOutput schema / properties / password_protected
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "slug",
-  "url",
-  "files",
-  "plan",
-  "expires_at"
-]New value: +[
+  "slug",
+  "url",
+  "files",
+  "plan",
+  "expires_at",
+  "password_protected"
+]

Changed1 schema field changedSep 1, 2026

changedInput schema / properties / ttl / description

Previous value: -"Lifetime in seconds (min 60). Anonymous: max 604800 (7 days), default 7 days. Signed-in free: max 2592000 (30 days), default 30 days. Paid: any value, omit for no expiry."New value: +"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."

Changed1 schema field changedAug 31, 2026

changedOutput schema / properties / slug / description

Previous value: -"Drop slug; the site is live at https://<slug>.shipped.page/"New value: +"Drop slug; the site is live at https://<slug>.shipped.run/"

Changed1 schema field changedAug 27, 2026

addedInput schema / properties / email

Added value: +{
+  "description": "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 human. Ignored for authenticated deploys (those are owned already).",
+  "type": "string"
+}

Changed1 schema field changedAug 21, 2026

changedInput schema / properties / ttl / description

Previous value: -"Lifetime in seconds (min 60). Free: max 604800 (7 days), default 7 days. Paid: any value, omit for no expiry."New value: +"Lifetime in seconds (min 60). Anonymous: max 604800 (7 days), default 7 days. Signed-in free: max 2592000 (30 days), default 30 days. Paid: any value, omit for no expiry."

Changed1 schema field changedAug 20, 2026

addedOutput schema / properties / claim_token

Added value: +{
+  "description": "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.",
+  "type": "string"
+}

First observedAug 18, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and non-idempotent, so the bar is lower. The description still adds real behavioral context: file-count ceilings, 30/90-day expiry windows, and the index.html serving requirement — all beyond what the annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the core purpose front-loaded before the tier/pricing detail. Dense but every clause carries usable information; only the pricing parenthetical is slightly extraneous for an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering the safety profile, the description only needs to add behavioral context, which it does via limits, expiry, and the index.html rule. Minor gap: no explicit statement of auth requirements or what a failed deploy returns, but those are largely covered elsewhere.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with rich per-parameter descriptions for ttl, name, password, and files, so the schema does the heavy lifting. The description's mention of 'named drops' and expiry adds only marginal framing beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (deploy) and resource (multi-file site) plus the critical index.html constraint for root serving. The 'map of path -> content' and 'multi-file' phrasing clearly distinguishes it from the sibling deploy_html and append_files.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides tier-based context (anonymous 100 files/30-day, Pro 900 files/custom TTL) that implicitly guides when the tool is usable, but never explicitly routes the agent between this and deploy_html or append_files for incremental updates. Usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ship.page tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?