Skip to content
MCPSTAMP
MCP server report

ShipMyForm MCP server

com.shipmyform/shipmyform

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 70 of 100 (grade C), higher than 11.0% of the 33,003 registry servers that responded over HTTPS that day. Ready for MCP Registry. Not ready for Claude, ChatGPT and Gemini.

Measured facts

Score
70C
Sign-in
OAuth
Tools listed
29
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by Protected resource metadata (RFC 9728), Authorization server metadata (RFC 8414 / OIDC) and readOnlyHint or destructiveHint on every tool.
ChatGPT app directory Not ready Blocked by Protected resource metadata (RFC 9728), Authorization server metadata (RFC 8414 / OIDC), readOnlyHint or destructiveHint on every tool and Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT).
Gemini Connected Apps Not ready Blocked by Authorization server metadata (RFC 8414 / OIDC).
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

6 checks to fix

  1. Fails

    readOnlyHint or destructiveHint on every tool

    tool_annotations

    Blocks Claude and ChatGPT.

    Measured 29/29 tools set neither readOnlyHint nor destructiveHint: sign_up, verify_account, resend_verification_code, get_account, create_api_key and 24 more

    Set annotations.readOnlyHint: true on read-only tools and destructiveHint: true on tools that modify or delete data (Claude needs one of them on every tool; ChatGPT needs all three hints, see tool_open_world).

  2. Fails

    Protected resource metadata (RFC 9728)

    auth_prm

    Blocks Claude and ChatGPT.

    Measured https://shipmyform.com/.well-known/oauth-protected-resource/api/mcp has no authorization_servers

    List your issuer URL in "authorization_servers" in the protected resource metadata.

  3. Fails

    Authorization server metadata (RFC 8414 / OIDC)

    auth_as_metadata

    Blocks Claude, ChatGPT and Gemini.

    Measured No authorization server to probe

    Serve RFC 8414 metadata at <issuer>/.well-known/oauth-authorization-server with authorization_endpoint, token_endpoint and response_types_supported ["code"].

  4. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 29/29 tools miss an explicit hint: sign_up, verify_account, resend_verification_code, get_account, create_api_key and 24 more

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

  5. Fails

    Tool descriptions

    tool_descriptions

    Measured 3/29 missing or under 20 chars: set_connector_active, remove_connector, unpublish_hosted_page

    Write a 1-3 sentence description for every tool: when to use it and what it returns.

  6. Warning

    initialize latency

    latency

    Measured 1621 ms

    Bring initialize under 1.5 s: avoid cold starts and upstream calls in the handshake.

15 checks passed, 6 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, GET answers SSE or 405, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), Resource metadata "resource" equals the server URL, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, Human-readable title on every tool.

Not run. 401 carries WWW-Authenticate resource_metadata, First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised. These need an OAuth sign-in flow the check could not reach.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for ShipMyForm

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fshipmyform.com%2Fapi%2Fmcp)](https://www.mcpstamp.com/r/com-shipmyform-shipmyform/)

HTML

<a href="https://www.mcpstamp.com/r/com-shipmyform-shipmyform/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fshipmyform.com%2Fapi%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Form backend as 29 tools: create endpoints, route submissions, publish pages, run the inbox.
Registry name
com.shipmyform/shipmyform
Remote URL
https://shipmyform.com/api/mcp
Version
1.1.0
Website
shipmyform.com/docs/mcp
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade C servers

All grade C servers · All server reports · State of MCP readiness, November 2026