Server providing Argo CD integration for MCP clients.
ShipStatic is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Deploy static sites instantly from AI agents — no account required
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mcp-shipstatic-com-shipstatic-mcp https://mcp.shipstatic.com/
# 2 — ask your agent for something these tools do
# deployments_upload, deployments_list, deployments_get and 12 more
ShipStatic costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, read from the address; if the publisher says otherwise, swap that one word.
claude mcp add --scope user --transport http mcp-shipstatic-com-shipstatic-mcp https://mcp.shipstatic.com/Reconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Deploy 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" per-file for binary content (images, fonts) — do not base64-encode text. Returns the live URL. Without a connected account, the response also includes a claim URL (
| Parameter | Type | Required | Notes |
|---|---|---|---|
| files | array | yes | Files that make up the site. The site root is implied by these paths. |
| labels | array | no | Labels for organizing deployments (e.g. ["production", "v1.2"]). Lowercase, 3-25 chars, allows . _ - separators. Up to 10. |
| password | string | no | Optional password to gate the deployment behind an unlock prompt (6–128 characters; whitespace significant). Visitors must enter this password before viewing the site, including on any custom domains |
| idempotencyKey | string | no | Makes this deploy replayable instead of repeatable. A deploy is not naturally idempotent: if a call times out you cannot tell "it never landed" from "it landed and the response was lost", and retrying |
| ttl | number | no | Seconds until this deployment expires and the platform reclaims it; omit for one that never does. Only for authenticated deploys — an anonymous deployment already expires on the platform's schedule, a |
List 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Maximum number of items to return in one page. Omit for the server default. |
| cursor | string | no | Opaque position from the previous response's cursor field; omit for the first page. |
Get deployment details including URL, status, file count, size, labels, and password protection state.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deployment | string | yes | Deployment hostname (e.g. "happy-cat-abc1234.shipstatic.com"). Returned by deployments_upload or deployments_list. |
Update deployment labels. Replaces all existing labels.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deployment | string | yes | Deployment hostname (e.g. "happy-cat-abc1234.shipstatic.com"). Use deployments_list to find deployments. |
| labels | array | yes | Labels to set. Replaces all existing labels. Pass empty array to clear. |
Permanently delete a deployment and its files. You MUST confirm with the user before calling this tool, referencing the deployment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deployment | string | yes | Deployment hostname to delete (e.g. "happy-cat-abc1234.shipstatic.com") |
Create or update a custom domain. Can reserve a name (omit deployment), link it to a deployment, switch deployments, or update labels. After creating, call domains_records and show the DNS records to the user.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name (e.g. "www.example.com" or "blog.example.com") |
| deployment | string | no | Deployment to serve on this domain (e.g. "happy-cat-abc1234.shipstatic.com"). Omit to reserve the domain without linking. |
| labels | array | no | Labels for organizing domains (e.g. ["production"]). |
List all domains with their URLs, linked deployment, and verification status. The response's cursor is null on the last page; pass it back as cursor to fetch the next.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Maximum number of items to return in one page. Omit for the server default. |
| cursor | string | no | Opaque position from the previous response's cursor field; omit for the first page. |
Get domain details including URL, linked deployment, verification status, and labels.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name (e.g. "www.example.com"). Use domains_list to find names. |
Get the DNS records the user needs to configure at their DNS provider. Call after domains_set. You MUST show the returned records to the user.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name. Must be a domain previously created with domains_set. |
Look up the DNS provider for a domain (e.g. Cloudflare, Namecheap). Helps the user know where to configure their DNS records.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name to look up DNS provider for (e.g. "www.example.com") |
Get a shareable DNS setup hash for a domain. The hash can be shared with the user so they can view the required DNS records without needing an API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name to generate a share link for. Must be a domain previously created with domains_set. |
Check if a domain name is valid and available before creating it. Returns the normalized form and availability.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name to check (e.g. "www.example.com"). Call before domains_set to check availability. |
Trigger DNS verification for a custom domain. Call after the user has configured DNS records from domains_records. Verification is asynchronous — the domain status updates once DNS propagates.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name to verify DNS for. Must be a domain previously created with domains_set. |
Permanently delete a domain. You MUST confirm with the user before calling this tool, referencing the domain name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name to delete (e.g. "www.example.com") |
Show authenticated account details including email, plan, and usage.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ShipStatic or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.3.5.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish ShipStatic can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.