Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Superforms

REMOTE · SUPERFORMS.CO · SCANNED SEP 27

Human-input bridge for AI agents with voice-first answer links, MCP tools, and HTTP APIs.

Available components

0 this week 73 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2670 tokens (~242/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 48% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "create_form" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Superforms MCP server?

Superforms is a hosted endpoint at https://superforms.co/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · superforms.co

# add to Claude Code
claude mcp add --transport http co-superforms-superforms 'https://superforms.co/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "co-superforms-superforms": {
      "url": "https://superforms.co/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "co-superforms-superforms": {
      "type": "http",
      "url": "https://superforms.co/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.co-superforms-superforms]
url = "https://superforms.co/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-superforms-superforms": {
      "type": "remote",
      "url": "https://superforms.co/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add co-superforms-superforms --url 'https://superforms.co/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  co-superforms-superforms:
    url: "https://superforms.co/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "co-superforms-superforms": {
      "Transport": "http",
      "Url": "https://superforms.co/mcp"
    }
  }
}
# add to Vellum
assistant mcp add co-superforms-superforms -t streamable-http -u 'https://superforms.co/mcp'
// mcp.json
{
  "mcpServers": {
    "co-superforms-superforms": {
      "type": "http",
      "url": "https://superforms.co/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Sept 26 +1
    • Stability: 0.97 → pass security
  • 2 Sept 26 −1
    • Stability: pass → 0.97 functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Aug 26 0
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “create_feedback_form” rewrote its description, which is the text the model reads security
    • Tool “create_form” rewrote its description, which is the text the model reads security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.30 ▲ functional
  • 3 Aug 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.23 → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 27 Sept 2026 · Probed https://superforms.co/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=superforms.co CN=YR1,O=Let's Encrypt,C=US 20 Sept 2026 19 Dec 2026 RSA 2048 SHA256-RSA 62fb31e36a1f1b074840aab6baf341ed5d0
SANs: superforms.co
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of superforms.co. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
co. present 7786 8 Verified
superforms.co. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://superforms.co/mcp Verified 200
http (plaintext) http://superforms.co/mcp HTTPS enforced 308 https://superforms.co/mcp
MCP tools · 11 exposed · ~1,506 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_ask ~294

Create a voice-first Superforms answer link for human input. Backward-compatible alias for create_form.

NameTypeReqDescription
contextstring–Private context for smart follow-ups. Summarize relevant non-sensitive host-conversation context and append any extra context the creator provides. Never shown to respondents.
creationSessionUrlstring––
followUpModestring–For exactly one question, set this only after asking the creator "Want smart follow-up questions?" Use deep_dive for yes or none for no. For multiple questions, use none unless explicitly requested.
goalstring––
max_followups_per_questionnumber–Optional compatibility setting. Omit for adaptive one-question smart follow-ups.
max_total_questionsnumber–Optional compatibility setting. Omit for adaptive one-question smart follow-ups.
persistentboolean––
promptstring–Plain-English ask or request. Use only when explicit questions are not already known.
questionContextobject––
questionsarray–Explicit questions to ask the respondent. Use this whenever questions already exist; preserve them exactly.
responseLimitstring–Use "one" for a form intended for one named person/client. Use "multiple" for forms, surveys, feedback, customers, users, and public/embedded links.
responseModestring––
titlestring––

No output schema declared.

No examples provided.

create_feedback_form ~301

Publish a voice-first feedback, cancellation, feature request, survey, or research form immediately after creator confirmation, with optional smart follow-ups.

NameTypeReqDescription
contextstring–Private context for smart follow-ups. Summarize relevant non-sensitive host-conversation context and append any extra context the creator provides. Never shown to respondents.
creationSessionUrlstring––
followUpModestring–For exactly one question, set this only after asking the creator "Want smart follow-up questions?" Use deep_dive for yes or none for no. For multiple questions, use none unless explicitly requested.
goalstring––
max_followups_per_questionnumber–Optional compatibility setting. Omit for adaptive one-question smart follow-ups.
max_total_questionsnumber–Optional compatibility setting. Omit for adaptive one-question smart follow-ups.
persistentboolean––
promptstring–Plain-English ask or request. Use only when explicit questions are not already known.
questionContextobject––
questionsarray–Explicit questions to ask the respondent. Use this whenever questions already exist; preserve them exactly.
responseLimitstring–Use "one" for a form intended for one named person/client. Use "multiple" for forms, surveys, feedback, customers, users, and public/embedded links.
responseModestring––
titlestring––

No output schema declared.

No examples provided.

create_form ~296

Publish a voice-first form link immediately after creator confirmation, collect human answers, and pipe responses back to the agent.

NameTypeReqDescription
contextstring–Private context for smart follow-ups. Summarize relevant non-sensitive host-conversation context and append any extra context the creator provides. Never shown to respondents.
creationSessionUrlstring––
followUpModestring–For exactly one question, set this only after asking the creator "Want smart follow-up questions?" Use deep_dive for yes or none for no. For multiple questions, use none unless explicitly requested.
goalstring––
max_followups_per_questionnumber–Optional compatibility setting. Omit for adaptive one-question smart follow-ups.
max_total_questionsnumber–Optional compatibility setting. Omit for adaptive one-question smart follow-ups.
persistentboolean––
promptstring–Plain-English ask or request. Use only when explicit questions are not already known.
questionContextobject––
questionsarray–Explicit questions to ask the respondent. Use this whenever questions already exist; preserve them exactly.
responseLimitstring–Use "one" for a form intended for one named person/client. Use "multiple" for forms, surveys, feedback, customers, users, and public/embedded links.
responseModestring––
titlestring––

No output schema declared.

No examples provided.

get_my_form_responses ~53

Read persisted raw responses for a form owned by the connected Superforms account. No per-form agent token is required.

NameTypeReqDescription
askIdstringyes–
sincestring–Optional ISO timestamp cursor.

No output schema declared.

No examples provided.

get_responses ~54

Fetch persisted raw responses for a Superforms ask. This is the MCP equivalent of the HTTP bridge answers endpoint.

NameTypeReqDescription
agentTokenstringyes–
askIdstringyes–
sincestring––

No output schema declared.

No examples provided.

join_creation_session ~65

Join a Superforms homepage creation handoff session before creating the real form. Pass agentName with the client name, such as Codex, Claude Code, Claude, ChatGPT, or Cursor.

NameTypeReqDescription
agentNamestring––
creationSessionUrlstringyes–

No output schema declared.

No examples provided.

list_asks ~27

List recent asks for a provided private agent token.

NameTypeReqDescription
agentTokenstringyes–

No output schema declared.

No examples provided.

list_my_forms ~27

List forms owned by the connected Superforms account, including response counts and latest response timestamps.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

update_creation_session ~202

Update a homepage creation handoff draft with the current form title, questions, and settings before the user clicks Set live.

NameTypeReqDescription
contextstring–Private smart-follow-up context. Summarize relevant non-sensitive host-conversation context and append any extra context the creator provides. Never shown to respondents.
creationSessionUrlstringyes–
followUpModestring––
goalstring––
max_followups_per_questionnumber–Use 0 by default. Use 1 only when smart follow-ups are explicitly requested.
max_total_questionsnumber–Use 20 for deep-dive interviews.
questionsarray–Current draft questions to show in the live form preview.
responseLimitstring–Use one for a named person/client. Use multiple for feedback forms, surveys, customers, users, and public links.
responseModestring––
titlestring––

No output schema declared.

No examples provided.

watch_ask ~113

Return as soon as an individual answer is saved, including answers received while an agent was reconnecting and while the form remains in progress. Use since for durable per-answer catch-up; the HTTP bridge also exposes an SSE stream endpoint.

NameTypeReqDescription
agentTokenstringyes–
askIdstring––
sincestring–ISO timestamp cursor from the last response the agent processed.
timeoutMsnumber–Maximum wait in milliseconds, capped at 120000.
urlstringyes–

No output schema declared.

No examples provided.

watch_my_form_responses ~74

Return any existing individual answers immediately, or wait briefly until the respondent saves their next answer, even while the form remains in progress.

NameTypeReqDescription
askIdstringyes–
sincestring–Optional ISO timestamp cursor.
timeoutMsnumber–Maximum wait in milliseconds, capped at 120000.

No output schema declared.

No examples provided.

Common questions

What is the Superforms MCP server?

Superforms is an MCP server listed in the public MCP registry as co.superforms/superforms. Human-input bridge for AI agents with voice-first answer links, MCP tools, and HTTP APIs. This page covers its hosted endpoint (https://superforms.co/mcp).

Is the Superforms MCP server safe to use?

Superforms scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Superforms MCP server expose?

Superforms exposes 11 tools: create_form, create_feedback_form, create_ask, join_creation_session, update_creation_session, and 6 more. Their descriptions and schemas cost roughly 1,506 tokens of context every time the server is loaded.

Does the Superforms MCP server require authentication?

No. We connected to Superforms without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Superforms MCP server still maintained?

Superforms is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.