Developer Tools
ship.page
Deploys HTML files and multi-file websites to live, unguessable URLs for quick sharing and testing.
ENDPOINT 1
https://ship.page/mcp
MCP server metadata
- Name
- ship.page
- Version
- 1.0.0
ship.page turns HTML (or a set of files) into a live, unguessable https://<slug>.shipped.run/ URL. Deploy works anonymously; send an sp_ API key as 'Authorization: Bearer sp_...' (or ?apiKey=sp_... on the endpoint URL) for named drops, appending, listing, restore and deletion. Anonymous deploys return a one-time claim_token (spc_...) that can later attach the drop to an account via claim_drop. Pro/Team can password-protect drops; never put passwords in URLs. Use get_limits for the full plan matrix.
Known tools 11
deploy_htmlDeploy one HTML document and get back a live, unguessable https://<slug>.
Inferred read-onlydeploy_filesDeploy a map of path -> content as a multi-file site (must include index.
Inferred read-onlyappend_filesAdd 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.
Potential side effectslist_dropsList drops owned by the authenticated account (requires an sp_ API key; anonymous drops are not listable).
Inferred read-onlyclaim_dropAttach an anonymously deployed drop to the authenticated account using its one-time claim token (spc_.
Potential side effectsrestore_dropBring back an expired drop owned by the authenticated account while its files are still retained (requires an sp_ API key).
Potential side effectsdelete_dropPermanently delete a drop owned by the authenticated account (requires an sp_ API key).
Potential side effectsremove_drop_passwordRemove password protection from a drop you own, making it readable by anyone with its URL.
Potential side effectsget_accountShow the authenticated account's plan, subscription status and usage (requires an sp_ API key).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.ship-page]
url = "https://ship.page/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"ship-page": {
"type": "http",
"url": "https://ship.page/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: ship-page
Remote MCP URL: https://ship.page/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"ship-page": {
"url": "https://ship.page/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"ship-page": {
"type": "http",
"url": "https://ship.page/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "ship-page",
"transport": "streamable-http",
"url": "https://ship.page/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for ship.page was fetched 2026-09-13T11:35:17.592Z.
ship.page is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.