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.

SurveysAI – Survey Builder for Google Forms

REMOTE · MCP.FOR-GOOGLE-FORMS.SURVEYSAI.COM

Create real Google Forms from plain-text survey questions, in your own Google account.

+4 this week 77 Trust /100

Last scanned (18 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Documents and Files

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 413 tokens (~68/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (17% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 71

    First indexed and scored.

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 21 Nov 2026 · Probed https://mcp.for-google-forms.surveysai.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.for-google-forms.surveysai.com CN=YR1,O=Let's Encrypt,C=US 2 Oct 2026 31 Dec 2026 RSA 2048 SHA256-RSA 6be21502f42a388435be7c5a19bb120f44d
SANs: mcp.for-google-forms.surveysai.com
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 mcp.for-google-forms.surveysai.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
surveysai.com. No DS 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.for-google-forms.surveysai.com/mcp Verified 200
http (plaintext) http://mcp.for-google-forms.surveysai.com/mcp HTTPS enforced 301 https://mcp.for-google-forms.surveysai.com/mcp
MCP tools · 6 exposed · ~326 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_google_form ~105

Creates the survey as a Google Form in the signed-in user's own Google account and returns its link. Call only after the user has agreed to the title and questions.

NameTypeReqDescription
form_textstringyesSurvey definition in the SurveysAI plain-text format (see get_capabilities). Maximum 100000 characters.
idempotency_keystring–Optional key (max 128 characters). Retrying with the same key and text returns the original form instead of creating another one.

No output schema declared.

No examples provided.

get_account_status ~51

Returns the signed-in user's plan, the maximum number of questions per form, whether a Google account is linked and whether SurveysAI may create Google Forms in it (google_forms_access: granted, missing or unknown).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_capabilities ~32

Returns the supported question types, the plain-text format reference and plan limits. Call this once before drafting a survey.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_profile ~22

Returns the signed-in user's stable pseudonymous id, name and email.

Input schema present but exposes no named parameters.

NameTypeReqDescription
emailstring––
idstringyes–
namestring––
nicknamestring––

No examples provided.

parse_form ~64

Parses a survey written in the SurveysAI plain-text format and returns the title, form description, questions, errors and warnings. Creates nothing.

NameTypeReqDescription
form_textstringyesSurvey definition in the SurveysAI plain-text format (see get_capabilities). Maximum 100000 characters.

No output schema declared.

No examples provided.

validate_form ~52

Runs deterministic checks on a survey draft and returns issues with suggestions. Creates nothing.

NameTypeReqDescription
form_textstringyesSurvey definition in the SurveysAI plain-text format (see get_capabilities). Maximum 100000 characters.

No output schema declared.

No examples provided.

Install

How do I install the SurveysAI – Survey Builder for Google Forms MCP server?

SurveysAI – Survey Builder for Google Forms is a hosted endpoint at https://mcp.for-google-forms.surveysai.com/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 · mcp.for-google-forms.surveysai.com

# add to Claude Code
claude mcp add --transport http com-surveysai-for-google-forms 'https://mcp.for-google-forms.surveysai.com/mcp'
Common questions

What is the SurveysAI – Survey Builder for Google Forms MCP server?

SurveysAI – Survey Builder for Google Forms is an MCP server listed in the public MCP registry as com.surveysai/for-google-forms. Create real Google Forms from plain-text survey questions, in your own Google account. This page covers its hosted endpoint (https://mcp.for-google-forms.surveysai.com/mcp).

Is the SurveysAI – Survey Builder for Google Forms MCP server safe to use?

SurveysAI – Survey Builder for Google Forms scores 77 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 SurveysAI – Survey Builder for Google Forms MCP server expose?

SurveysAI – Survey Builder for Google Forms exposes 6 tools: get_capabilities, parse_form, validate_form, create_google_form, get_profile, get_account_status. Their descriptions and schemas cost roughly 326 tokens of context every time the server is loaded.

Does the SurveysAI – Survey Builder for Google Forms MCP server require authentication?

No. We connected to SurveysAI – Survey Builder for Google Forms without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SurveysAI – Survey Builder for Google Forms MCP server still maintained?

SurveysAI – Survey Builder for Google Forms is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the SurveysAI – Survey Builder for Google Forms MCP server?

VerifyMCP ran 13 checks on SurveysAI – Survey Builder for Google Forms, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.