ShipStatic MCP server
Which servers in the official MCP registry are ShipStatic's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-20
- Registry namecom.shipstatic/mcpverified in the MCP registry
The registry name sits under shipstatic.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-20
- Tools15
- Server calls itselfshipstatic
- Server version2.7.0
- Protocol version2025-06-18
On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 228 ms.
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer225 ms
- Space in an agent's context≈ 2,527 tokensthe definitions of all its tools (15), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Every tool passes all six checks.
Worth a look
- Tools that change data, on a server that answers without a sign-in: deployments_upload, deployments_set, deployments_delete, domains_set, domains_delete
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →
deployments_uploadDeploy a static site to a live URL: free, no account or API key required. **File content is plain text by default.** Pass HTML/CSS/JS/JSON/SVG/etc. directly in each file's `content` as a regular string. Only set `encoding: "base64"`…
deployments_listList all deployments with their URLs, status, labels, and password protection state. The response's `cursor` is null on the last page; pass it back as `cursor` to fetch the next.
deployments_getGet deployment details including URL, status, file count, size, labels, and password protection state.
deployments_setUpdate deployment labels. Replaces all existing labels.
deployments_deletePermanently deletes a deployment and its files.
domains_setCreate or update a domain: a ShipStatic domain (e.g. "yourname.shipstatic.com"), live as soon as a deployment is linked, or a custom domain (e.g. "www.example.com"), which needs DNS records first. Can reserve a name (omit deployment)…
domains_listList all domains with their URLs, linked deployment, and `status`. The response's `cursor` is null on the last page; pass it back as `cursor` to fetch the next.
domains_getGet domain details including URL, linked deployment, labels, and `status`: the one word saying what the domain needs from its owner (`unverified`, `unlinked`, `live`, `paused`).
domains_recordsReturns the DNS records to configure at the domain's DNS provider. Call after domains_set. Custom domains only: a ShipStatic domain has no records to configure.
domains_dnsReturns the DNS provider recorded for the domain, if known (e.g. Cloudflare, Namecheap): where its DNS records are configured. Custom domains only, and only while the domain is unverified; once its DNS is right there is nothing left to…
domains_shareReturns a shareable DNS setup URL that needs no API key, for whoever manages the domain's DNS. Custom domains only, and only while the domain is unverified; a verified domain has no setup left to share.
domains_validateCheck if a domain name is valid and available before creating it. Returns the normalized form and availability.
domains_verifyTrigger DNS verification for a custom domain. Call after the user has configured DNS records from domains_records. Custom domains only, and refused once the domain is verified: read domains_get instead. Verification is asynchronous: read…
domains_deletePermanently deletes a domain.
whoamiReturns your email and name, and the account's plan, usage and caps.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"shipstatic": {
"type": "http",
"url": "https://mcp.shipstatic.com"
}
}
}Also shipped through: npm
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.