Is the Shipmyform MCP server down?

mcp-registry/com.shipmyform/shipmyform · v2.0.0

healthy
Last checked 2026-10-18 02:20 UTC · handshake 744ms

As of 2026-10-18 02:20 UTC, the Shipmyform MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
2,248
outages (90d)
0
tools
29

Create form endpoints for any site, get paste-ready markup, and read submission stats.

Install Shipmyform MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http shipmyform-mcp-server https://shipmyform.com/api/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "shipmyform-mcp-server": {
      "type": "http",
      "url": "https://shipmyform.com/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (67/100)

D (67/100): 1 error(s), 3 warning(s) across 29 tool(s); ~3,853 tokens of tool definitions.
Scores higher than 2% of 15,350 MCP servers Glimind has audited.
Its tool list costs an agent ~3,853 tokens per session — more than 55% of servers.
no tool-poisoning patterns
Schemas100
Descriptions33
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability96

What to fix (6)

3 tool(s) have no description.

Describe what each tool does, when to use it and what it returns in one or two sentences. Models choose tools almost entirely from this text.

Tools: remove_connector, set_connector_active, unpublish_hosted_page

29 of 29 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.

Tools: add_connector, create_api_key, create_form, delete_form, delete_submissions and 24 more

29 parameter(s) across 15 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.

Tools: create_api_key, delete_submissions, export_submissions, get_form_snippet, get_submission and 10 more

10 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.

Tools: create_api_key, create_form, delete_form, delete_submissions, publish_hosted_page and 5 more

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.

In the last 30 days: 0 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts.

Auto-fix: 24 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 15 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.shipmyform%2Fshipmyform/fixes

add_connector 1 change
{
  "name": "add_connector",
  "description": "Route a form's submissions somewhere: email, webhook, Slack, Discord, Airtable, HubSpot, Telegram and more. Get the config fields from list_connector_types. OAuth connectors (Google Sheets, Notion) must be added in the dashboard.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "formId",
      "type",
      "config"
    ],
    "properties": {
      "type": {
        "type": "string",
        "description": "Connector type from list_connector_types, e.g. 'slack'"
      },
      "config": {
        "type": "object",
        "description": "Field values keyed by the config field names",
        "propertyNames": {
          "type": "string"
        },
        "additionalProperties": {}
      },
      "formId": {
        "type": "string",
        "description": "Form id, e.g. frm_abc123"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Add a connector"
}
create_api_key 1 change
{
  "name": "create_api_key",
  "description": "Mint another API key for this workspace (shown once), optionally narrower than this one. A key can never grant scopes it does not itself hold, so this is the safe way to hand a limited key to another agent.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "maxLength": 80,
        "minLength": 1
      },
      "preset": {
        "enum": [
          "full",
          "wiring",
          "readonly",
          "triage"
        ],
        "type": "string",
        "description": "Named scope bundle: full (everything), wiring (forms only, no submission access), readonly, triage"
      },
      "scopes": {
        "type": "array",
        "items": {
          "enum": [
            "forms:read",
            "forms:write",
            "forms:delete",
            "submissions:read",
            "submissions:write",
            "submissions:delete",
            "account:manage"
          ],
          "type": "string"
        },
        "description": "Explicit scopes, instead of a preset. Ignored where it would exceed the calling key's own scopes."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Create an API key"
}
create_form 1 change
{
  "name": "create_form",
  "description": "Create a form and get its endpoint plus a paste-ready HTML snippet. Email notifications to the account owner are set up automatically. Works on every plan.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "maxLength": 80,
        "minLength": 1,
        "description": "Human-readable form name, e.g. 'Contact form'"
      },
      "purpose": {
        "type": "string",
        "maxLength": 500,
        "description": "What the form is for, in a sentence. Helps the spam classifier."
      },
      "allowedDomains": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 20,
        "description": "Sites allowed to submit, e.g. ['example.com']. Empty = any."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Create a form"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.shipmyform/shipmyform"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.shipmyform/shipmyform"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.shipmyform%2Fshipmyform.svg)](https://glimind.com/server/mcp-registry%2Fcom.shipmyform%2Fshipmyform?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.shipmyform%2Fshipmyform?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.shipmyform%2Fshipmyform.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.shipmyform%2Fshipmyform.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.shipmyform%2Fshipmyform?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d78015d9a95157e3…, first seen 2026-10-17, included at leaf 1261 of 19,720. Version history · verify what your client received.

Tools (29)

Compare: most reliable data servers · most reliable security servers · most reliable productivity servers · most reliable retrieval servers · most reliable finance servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Shipmyform MCP server down right now?

As of 2026-10-18 02:20 UTC, the Shipmyform MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Shipmyform MCP server provide?

Shipmyform MCP server advertises 29 tools, including add_connector, create_api_key, create_form, delete_form, delete_submissions.

How do I install Shipmyform MCP server?

Point your MCP client at this streamable-http endpoint: https://shipmyform.com/api/mcp

Is the Shipmyform MCP server safe to connect to an AI agent?

Glimind scanned all 29 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Shipmyform MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.