Servidor MCP de ShipMyForm
Qué servidores del registro oficial de MCP son de ShipMyForm, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.
leído el 2026-10-19
- Nombre en el registrocom.shipmyform/shipmyformverificado en el registro MCP
El nombre en el registro está bajo shipmyform.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.
- Estadorespondecomprobado el 2026-10-19
- Herramientas29
- El servidor se llamashipmyform
- Versión del servidor2.0.0
- Versión del protocolo2025-06-18
El 2026-10-19 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 300 ms.
- Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
- Mediana de la primera respuesta358 ms
- Espacio en el contexto del agente≈ 3473 tokenslas definiciones de todas sus herramientas (29), que el agente lleva en cada turno
- Definiciones de herramientasC · 73 de 100
- Sin una descripción con la que el agente pueda elegir: 3 de 29
- Parámetros sin descripción: en 15 de 29
- Sin indicar si solo lee o puede destruir: 29 de 29
Conviene revisar
- Herramientas que borran, envían o pagan sin avisar al cliente: revoke_api_key, delete_form, remove_connector, delete_submissions
- Herramientas que cambian datos, en un servidor que responde sin iniciar sesión: create_api_key, create_form, update_form, delete_form, add_connector
Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. El estado de los servidores MCP de los proveedores: método y números →
sign_upStart a ShipMyForm account from an email address, with no browser. A 6-digit code is emailed to the address; verify_account with { email, code } then returns the API key. Works without authentication. Also works for an existing account…
verify_accountProve the address with the 6-digit code emailed by sign_up. Without a key on the connection, pass the email too: on success this returns the API key (shown once). Turns on email notifications.
resend_verification_codeEmail a fresh 6-digit verification code to the account's address.
get_accountThe account's email, verification state, plan, limits, usage and dashboard URL.
create_api_keyMint 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.
list_api_keysAPI keys on this workspace (metadata only).
revoke_api_keyRevoke a key by id. The key in use on this connection cannot revoke itself.
start_upgradeGet a hosted checkout URL for the Starter or Business plan. Payment is completed by a person on that page; the plan activates automatically afterwards (check with get_account).
get_billing_portalA self-service billing portal URL: change plan, update the card, cancel.
list_formsThe workspace's forms with their public endpoint URLs.
create_formCreate 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.
get_formA form's full configuration, connectors and hosted-page status.
update_formChange any subset of a form's settings: name, purpose, allowedDomains, redirectUrl, spamMode, active, storeSubmissions, validation rules, blocklist, autoResponder (Pro).
delete_formDelete a form; its endpoint stops accepting submissions.
get_form_snippetA copy-paste form snippet for a framework (html, react, vue, or fetch) wired to the form's endpoint.
get_submission_statsDelivered / spam-held / flagged counts for a form, plus workspace quota usage. Works on every plan.
list_connector_typesEvery destination submissions can be routed to, with the config fields each needs and which plan it requires.
list_connectorsConnectors on a form with their status and last error.
add_connectorRoute 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.
test_connectorSend a test delivery through a connector and report the result.
set_connector_activeSin descripción.
remove_connectorSin descripción.
publish_hosted_pagePublish a standalone page for the form on shipmyform.com (no website needed) and get its URL plus an embed script. Uses the designed page if one exists, otherwise a default email + message form.
unpublish_hosted_pageSin descripción.
list_submissionsRead submissions across the workspace or for one form, with filters (status, date range, text search, country, attachments, failed deliveries) and paging. Spam is excluded unless status is 'spam'. Requires a paid plan.
get_submissionOne submission with spam signals and delivery history.
label_submissionsMark submissions as spam, ok (not spam) or flagged. spam/ok also teach the classifier, so your judgement improves future filtering. This is how you triage in your own environment: list, decide, label.
delete_submissionsPermanently delete submissions (and their files).
export_submissionsAll of a form's submissions (up to 2,000) as CSV text, optionally filtered by status.
Cómo conectar
Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:
{
"mcpServers": {
"shipmyform": {
"type": "http",
"url": "https://shipmyform.com/api/mcp"
}
}
}Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.