ship.page

Deploy a single HTML page

deploy_html

Destructive

Deploy one HTML document and get back a live, unguessable https://.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 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>.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.8/5.0

Behavior4/5

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

Annotations are limited to hints (non-read-only, open-world, non-idempotent, destructive), and the description goes well beyond them: rate limit per IP, body size cap, expiry behavior for anonymous deploys, and the unguessable-slug security property. It does not explain what a deploy overwrites when a name is reused, which is the behavior the destructiveHint implies.

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?

Three sentences, front-loaded with the action and its result, then tier constraints. Dense but every clause carries information; the mid-sentence tier enumeration is slightly list-like but not wasteful.

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

Completeness5/5

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

With an output schema present, the description need not explain return fields, and it still surfaces the key output (the live URL). It covers quotas, caps, and expiry tiers, which is enough for an agent to invoke it correctly; only the sibling routing decision is left unaddressed.

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% and the parameter docs are already detailed (ttl tiers, name/subscription requirement, email claim link, password rules). The description's mentions of TTL, named drops, and Pro tier restate that same information rather than adding syntax or edge-case detail the schema lacks, so the 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 gives a specific verb and resource (deploy one HTML document) plus the concrete outcome: a live unguessable https://<slug>.shipped.run/ URL. It is clear on its own, but it never names the obvious sibling deploy_files, so an agent has to guess whether a multi-file or single-file case routes here.

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?

Tier-based conditions are stated (anonymous 10 deploys/min, 10MB cap, 30-day expiry; Pro gets custom TTL and named drops), which implies when the tool is usable. But there is no explicit when-to-use-this-vs-deploy_files guidance and no stated prerequisites for named/password deploys.

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?