ship.page

Deploy a single HTML page

deploy_html

Destructive

Deploy one HTML document and get back a live, unguessable https://.ship.place/ URL. Anonymous: 10 deploys/min per IP, 10MB body cap, 30-day expiry. Pro ($4/mo): 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.
`html`	Yes	The full HTML document to publish.
`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).
`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>.ship.place/
`files`	Yes
`replaced`	No	Present with named deploys; true when an existing drop was replaced
`claim_url`	No	Present on anonymous deploys: a browser link that saves the drop to whichever account opens it. It carries the claim token, so keep it private.
`next_step`	No	Present with claim_url: one sentence on keeping the page online, written to be passed on to the person the page was made for.
`expires_at`	Yes	ISO timestamp, or null when the drop never expires
`claim_email`	No	Present when email was accepted on an anonymous deploy; the claim link was mailed to this address.
`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.

Changed3 schema fields changedOct 12, 2026

addedOutput schema / properties / claim_email

Added value: +{
+  "description": "Present when email was accepted on an anonymous deploy; the claim link was mailed to this address.",
+  "type": "string"
+}

addedOutput schema / properties / claim_url

Added value: +{
+  "description": "Present on anonymous deploys: a browser link that saves the drop to whichever account opens it. It carries the claim token, so keep it private.",
+  "type": "string"
+}

addedOutput schema / properties / next_step

Added value: +{
+  "description": "Present with claim_url: one sentence on keeping the page online, written to be passed on to the person the page was made for.",
+  "type": "string"
+}

Changed1 schema field changedSep 29, 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>.ship.place/"

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.8/5.0

Behavior4/5

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

Annotations already declare the write, destructive, non-idempotent, open-world profile, so the bar is lower. The description adds genuinely useful operational context the annotations lack: a 10 deploys/min per IP rate limit, a 10MB body cap, and the 30-day anonymous expiry.

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

Conciseness5/5

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

Two tight sentences with zero waste: the core action and return value come first, followed by the tier/limit facts. Nothing is padded or redundant.

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?

An output schema exists, so return values need no narration, and the description plus rich parameter docs cover the essentials. It is close to complete; a brief pointer to the claim/restore lifecycle for anonymous drops would close the remaining gap.

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 description coverage is 100%, so the schema already documents ttl, name, password, email, and agent with their constraints. The description's tier/expiry remarks echo rather than extend the schema, so baseline 3 applies.

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

Purpose4/5

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

The description states a specific verb (Deploy) and resource (one HTML document) and describes the output (a live, unguessable URL). It implicitly separates itself from deploy_files by stressing a single document, but never names that sibling explicitly to remove all doubt.

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?

It conveys tier-based capabilities (Anonymous limits vs Pro custom/no TTL and named drops), which gives context on what's possible, but never states when to choose this over deploy_files or how the deploy/claim/restore lifecycle relates. Usage is implied rather than directed.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?