Evidra vs Shipstatic MCP

A side-by-side look at the Evidra and Shipstatic MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Evidra logoEvidraCloud PlatformsFail-closed policy guardrails for AI agents running kubectl, terraform, helm, and argocd.35FairAuth: not declaredShipstatic MCP logoShipstatic MCPCloud Platforms · Local subprocess (stdio)Deploy and manage static sites from AI agents. A simpler alternative to Vercel and Netlify for static website hosting — upload files, get a URL, and connect custom domains.67GreatAuth: no auth required

Verdict: choose Evidra for cloud platforms work; choose Shipstatic MCP for cloud platforms as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Evidra logoChoose Evidra when

  • You need dedicated capabilities in the Cloud Platforms domain.
Explore Evidra

Shipstatic MCP logoChoose Shipstatic MCP when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You have the keys it needs: SHIP_TOKEN.
  • You want tools like deployments_upload, deployments_list, deployments_get.
Explore Shipstatic MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecEvidra logoEvidraShipstatic MCP logoShipstatic MCP
CategoryCloud PlatformsCloud Platforms
Quality signal35/100 · Fair67/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedSHIP_TOKEN
Verified ownerCommunity listingCommunity listing
GitHub stars156
Directory activity 3 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
ToolsNot listed15

Tools & capabilities

Evidra tools

No tool names declared yet. Check the project README from the listing page.

Shipstatic MCP tools 15

  • deployments_uploadDeploy a static site instantly: free, no account or API key required. Returns the live URL, file count, and size. Without SHIP_TOKEN, the response also includes a one-time claim URL, and the site expires in 3 days unless claimed. Pass `password` to make the site private.
  • 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 custom domain. Can reserve a name (omit deployment), link it to a deployment, switch deployments, or update labels. domains_records then returns the DNS records to configure.
  • 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 locate.
  • 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.
  • +3 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Evidra

No confirmed install command for Evidra yet — follow the setup steps linked from its listing page rather than a guessed package name.

Shipstatic MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "shipstatic-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@shipstatic/mcp"
      ],
      "env": {
        "SHIP_TOKEN": "YOUR_SHIP_TOKEN_HERE"
      }
    }
  }
}

Frequently asked questions

Evidra is categorized under Cloud Platforms and uses an install path we have not confirmed yet. Shipstatic MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick Evidra for cloud platforms work and Shipstatic MCP for cloud platforms.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Evidra has no confirmed install command yet — follow its own setup instructions.

Evidra has no declared pricing — check the project's own site. Shipstatic MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add evidra-2 and shipstatic-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Evidra has a quality signal of 35/100 (Fair) with 3 views, 0 installs and 15 GitHub stars. Shipstatic MCP has 67/100 (Great) with 7 views, 0 installs and 6 GitHub stars.