Developer · Remote MCP server
ship.page
Deploy HTML from any agent: POST markup, get a live URL. Static hosting API with MCP tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
page.ship/ship-page- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-18
- Updated
- 2026-08-18
- Publisher
- page.ship
- Namespace
- Namespace verified by the MCP Registry via the domain ship.page · how
- Website
- ship.page
- Repository
- github.com/bitgate/ship.page
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://ship.page/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- ship.page 1.0.0 · protocol 2025-06-18
- Tools discovered
- 11:
deploy_html,deploy_files,append_files,list_drops,claim_drop,restore_drop,delete_drop,set_drop_password,remove_drop_password,get_limits,get_account - Checked on
- 2026-10-05
How to connect ship.page
ship.page is a remote MCP server: there is nothing to install. Its endpoint is https://ship.page/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| shieldly-io MCPAI-Powered AWS security analysis: scan IAM policies and CloudFormation for risks and escalation. | Local · stdio |
| Shift MCP ServerLightweight coordination layer for multiple AI agents working on the same codebase simultaneously. | Local · stdio, HTTP |
| ShimguardWraps the ShimGuard CLI as a single generic MCP tool for agent-shim provenance checks. | Local · stdio |
| Ship MCPClean TypeScript starter for MCP servers: zod-validated tools, tests, one-command dev loop. | Local · stdio |
| ShipbookDebug production issues using Shipbook logs and Loglytics error insights. | Remote · HTTPLive check: sign-in required |
| Shipcheck MCPRead-only Shipcheck launch-risk scans for authorized JS, TS, and MCP repos. | Local · stdio |
| ShipDappDeploy Dockerized apps to Akash devnet with ShipDapp MCP build, deploy, update, and logs tools. | Remote · SSELive check: ✓ SSE reachable |
| ShipedDeploy AI-generated HTML/CSS/JS to instant public HTTPS URLs from any MCP-compatible agent. | Remote · HTTPLive check: ✓ handshake |