MCP.so
ログイン

ship.page MCP Server認証済み注目

@Bitgate

基本情報

トランスポート

Streamable HTTP

認証方式

不要

カテゴリ

開発者ツール

作者

Bitgate

投稿者

Bart Pelle

ship.page MCP Server について

Throw HTML at an API, get an unguessable URL back. Zero-config remote MCP server — your agent deploys pages, sites and CI reports in one call. Free, no signup needed.

接続情報

https://ship.page/mcp

セットアップ

claude mcp add ship-page --transport http https://ship.page/mcp

ship.page MCP Server のツール

11

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

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

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.

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.

Attach an anonymously deployed drop to the authenticated account using its one-time claim token (spc_..., returned once by deploy_html/deploy_files). Claiming extends the drop to the free-account lifetime (90 days) and can revive an offline drop during its 30-day private recovery window. Claimed drops become listable, deletable, and — on paid plans — redeployable via named drops. Requires an sp_ API key.

Bring back an expired drop owned by the authenticated account while its files are still retained (requires an sp_ API key), up to 90 days past expiry. Free accounts get the drop back at the 90-day lifetime; on a paid plan the restored drop never expires again.

Permanently delete a drop owned by the authenticated account (requires an sp_ API key). The URL stops serving immediately and cannot be recovered.

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.

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.

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.

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.

概要

Throw HTML at an API, get back a live URL. ship.page is the fastest way for an AI agent to put content on the public internet — deploy pages, multi-file sites, and CI reports in one call, then hand your human a link. Free, no signup, no OAuth dance.

What agents use it for

  • Preview deploys — render a mockup, report, or dashboard and share it instantly
  • CI artifacts — Playwright reports, coverage HTML, build output; first-class GitHub Action and plain-curl flows
  • One-off pages — every deploy gets an unguessable *.shipped.page subdomain, mounted at root so absolute paths just work

How it works

POST your markup and get JSON back with a live url:

curl -X POST https://ship.page/deploy \
  -H "Content-Type: text/html" \
  --data-binary @report.html

Three body formats: raw HTML, a JSON path → content files map (base64 for binaries), or a full zip of a build folder. Anonymous drops live for 7 days, no account required.

MCP tools

Deploy and manage drops straight from your agent: deploy_html, deploy_files, list_drops, claim_drop, delete_drop, get_limits — plus structured JSON errors with human-readable hints your agent can relay verbatim when something's plan-gated.

Auth is optional pass-through: no key = anonymous deploys, Authorization: Bearer sp_… = the tools act as that account (30-day drops, higher limits, named drops on Pro).

Config:

{
  "mcpServers": {
    "ship.page": { "url": "https://ship.page/mcp" }
  }
}

Full API also published as an OpenAPI 3.1 spec at ship.page/openapi.json. Docs: ship.page/docs/agents

よくある質問

1

ship.page のリモート MCP サーバーとは何ですか?

ship.page のリモート MCP サーバーは、https://ship.page/mcp にホストされた Model Context Protocol エンドポイントです。AI アシスタントはローカルに何もインストール・実行することなく接続できます。

2

ship.page の MCP サーバーにはどう接続しますか?

エンドポイント https://ship.page/mcp を Claude Code、Cursor、VS Code など任意の MCP 対応クライアントに追加してください。このページのセットアップ手順で各クライアントを一度に設定できます。

3

ship.page の MCP サーバーは認証が必要ですか?

いいえ。ship.page の MCP サーバーは認証不要です——エンドポイント URL で直接接続できます。

4

ship.page の MCP サーバーはどのトランスポートを使用しますか?

ship.page は Streamable HTTP エンドポイントを公開しており、これはリモート MCP サーバーで広く使われ、主要な MCP クライアントがサポートするトランスポートです。

コメント