Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ship.page

REMOTE · SHIP.PAGE

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

Available components

−1 this week 80 Trust /100

Last scanned (22 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Cloud Infrastructure

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1673 tokens (~152/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
Changelog

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.

  • 4 Nov 26 −1
    • Tool “claim_drop” rewrote its description, which is the text the model reads security
    • Tool “deploy_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 “restore_drop” rewrote its description, which is the text the model reads security
    • “deploy_files” reworded the description of “ttl” cosmetic
    • “deploy_html” reworded the description of “ttl” cosmetic
  • 3 Nov 26 0
    • Tool “restore_drop” rewrote its description, which is the text the model reads security
  • 12 Oct 26 0
    • Tool “append_files” rewrote its description, which is the text the model reads security
    • Tool “deploy_files” rewrote its description, which is the text the model reads security
  • 1 Oct 26 81
    • Tool “restore_drop” rewrote its description, which is the text the model reads security
  • 30 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
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 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
Diagnostics

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 4 Nov 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 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA256 8771c93aea4b36370e0eb4266bdf11ed
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
MCP tools · 11 exposed · ~1,545 tokens

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 →

Tool Tokens
append_files ~121

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

NameTypeReqDescription
filesobjectyesMap of relative paths (e.g. 'index.html', 'css/app.css') to either a string, or { encoding: 'base64', content } for binary files.
slugstringyesThe drop slug (the subdomain part of its ${domain} URL).
NameTypeReqDescription
expires_atstring|nullyesISO timestamp, or null when the drop never expires
filesarrayyesPaths added by this call
planstring––
slugstringyes–
total_filesintegeryesTotal files on the drop after the append
urlstringyes–

No examples provided.

claim_drop ~144

Attach an anonymously deployed drop to the authenticated account using its one-time claim token (spc_..., returned once by deploy_html/deploy_files). Claiming a live drop extends it to the free-account lifetime (30 days). A drop that already expired can still be claimed, but it stays expired until it's restored on Pro. Claimed drops become listable, deletable, and — on paid plans — redeployable via named drops. Requires an sp_ API key.

NameTypeReqDescription
claim_tokenstringyesThe one-time spc_... token returned at deploy time.
slugstringyesThe drop slug (the subdomain part of its ${domain} URL).
NameTypeReqDescription
claimedbooleanyes–
expires_atstring|null–ISO timestamp after the claim's lifetime extension, or null
pausedboolean–True when the drop had already expired and joined the account offline; restoring it needs Pro
restoredboolean–True when the drop had already expired and was revived by the claim
slugstringyes–
urlstringyes–

No examples provided.

delete_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.

NameTypeReqDescription
slugstringyesThe drop slug (the subdomain part of its ${domain} URL).
NameTypeReqDescription
deletedstringyesSlug of the deleted drop

No examples provided.

deploy_files ~397

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, 7-day expiry (30 days once signed in). Pro ($4/mo): up to 10,000 files, custom or no TTL, named drops.

NameTypeReqDescription
agentstring–Name of the AI agent or app publishing this drop, e.g. 'chatgpt', 'claude', 'cursor'. AI agents: always set this.
emailstring–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…
filesobjectyesMap of relative paths (e.g. 'index.html', 'css/app.css') to either a string, or { encoding: 'base64', content } for binary files.
namestring–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.
passwordstring–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.…
ttlinteger–Lifetime in seconds (min 60). Anonymous: max 604800 (7 days), default 7 days. Signed-in free: max 2592000 (30 days), default 30 days. A longer ttl is capped at the max. Paid: any value, omit for no e…
NameTypeReqDescription
claim_emailstring–Present when email was accepted on an anonymous deploy; the claim link was mailed to this address.
claim_tokenstring–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.
claim_urlstring–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.
expires_atstring|nullyesISO timestamp, or null when the drop never expires
filesarrayyes–
hintstring–Present when the requested ttl was over the plan's maximum and was capped to it.
namestring––
next_stepstring–Present when an API or MCP deploy expires: when the page expires and how to keep it online, written to be passed on to the person the page was made for.
password_protectedbooleanyes–
planstringyes–
replacedboolean–Present with named deploys; true when an existing drop was replaced
slugstringyesDrop slug; the site is live at https://<slug>.ship.place/
urlstringyes–

No examples provided.

deploy_html ~360

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

NameTypeReqDescription
agentstring–Name of the AI agent or app publishing this drop, e.g. 'chatgpt', 'claude', 'cursor'. AI agents: always set this.
emailstring–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…
htmlstringyesThe full HTML document to publish.
namestring–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.
passwordstring–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.…
ttlinteger–Lifetime in seconds (min 60). Anonymous: max 604800 (7 days), default 7 days. Signed-in free: max 2592000 (30 days), default 30 days. A longer ttl is capped at the max. Paid: any value, omit for no e…
NameTypeReqDescription
claim_emailstring–Present when email was accepted on an anonymous deploy; the claim link was mailed to this address.
claim_tokenstring–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.
claim_urlstring–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.
expires_atstring|nullyesISO timestamp, or null when the drop never expires
filesarrayyes–
hintstring–Present when the requested ttl was over the plan's maximum and was capped to it.
namestring––
next_stepstring–Present when an API or MCP deploy expires: when the page expires and how to keep it online, written to be passed on to the person the page was made for.
password_protectedbooleanyes–
planstringyes–
replacedboolean–Present with named deploys; true when an existing drop was replaced
slugstringyesDrop slug; the site is live at https://<slug>.ship.place/
urlstringyes–

No examples provided.

get_account ~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.

NameTypeReqDescription
accountIdstringyes–
activeSubscriptionbooleanyes–
cancelAtstring|null––
currentPeriodEndstring|null––
planstringyesfree | pro | team
portalAvailableboolean––

No examples provided.

get_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.

NameTypeReqDescription
accountobject–Present when an sp_ API key was supplied
plansobjectyesPlan matrix: anonymous, pro, team

No examples provided.

list_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.

NameTypeReqDescription
limitinteger–Max drops to return (1-500, default 100).
offsetinteger–Number of drops to skip (default 0).
NameTypeReqDescription
dropsarrayyes–
totalintegeryes–

No examples provided.

remove_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.

NameTypeReqDescription
slugstringyesThe drop slug (the subdomain part of its URL).
NameTypeReqDescription
password_protectedbooleanyes–
slugstringyes–

No examples provided.

restore_drop ~82

Bring back an expired drop owned by the authenticated account, however long ago it expired (requires an sp_ API key on a paid plan). The restored drop doesn't expire while the account stays on Pro. Free accounts get a 402 subscription_required with an upgrade_url.

NameTypeReqDescription
slugstringyesThe drop slug (the subdomain part of its ${domain} URL).
NameTypeReqDescription
expires_atstring|nullyesISO timestamp after the restore, or null when the drop never expires
restoredbooleanyesFalse when the drop was not expired and nothing changed
slugstringyes–
urlstringyes–

No examples provided.

set_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.

NameTypeReqDescription
passwordstringyesShared 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.…
slugstringyesThe drop slug (the subdomain part of its URL).
NameTypeReqDescription
password_protectedbooleanyes–
slugstringyes–

No examples provided.

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.

remote · ship.page

# add to Claude Code
claude mcp add --transport http page-ship-ship-page 'https://ship.page/mcp'
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 80 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,545 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.