SurveysAI – Survey Builder for Google Forms MCP server
com.surveysai/for-google-formssurveysai.comstreamable-httpv1.0.0Scanned
Create real Google Forms from plain-text survey questions, in your own Google account.
6 tools: 3 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the SurveysAI – Survey Builder for Google Forms MCP server can do
The SurveysAI – Survey Builder for Google Forms MCP server is published by surveysai.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (3 tools: parse_form, validate_form and create_google_form), but cannot delete data. 3 tools only read.
1 tool reads private data (get_profile); 2 tools bring in text other people can write (create_google_form and get_profile).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 9, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 3Claude Code: ask
create_google_formCreates the survey as a Google Form in the signed-in user's own Google account and returns its link.Reads text others writeNo findings
Why it is in this group
- The name "create_google_form" says "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Create a Google Form
parse_formParses a survey written in the SurveysAI plain-text format and returns the title, form description, questions, errors and warnings.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Parses a survey written in the SurveysAI plain-text format and returns the title, form description, questions, errors and warnings. Creates nothing.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Parse a survey draft
validate_formRuns deterministic checks on a survey draft and returns issues with suggestions.1 finding
Why it is in this group
- The name "validate_form" says "validate": a word for reading.
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "validate_form" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "validate_form" says "validate": a word for reading.
Description, as the server wrote it Runs deterministic checks on a survey draft and returns issues with suggestions. Creates nothing.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Validate a survey draft
Only reads 3Show 3 read-only tools
get_account_statusReturns 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_ac…No findings
Why it is in this group
- The name "get_account_status" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Get account status
get_capabilitiesReturns the supported question types, the plain-text format reference and plan limits.No findings
Why it is in this group
- The name "get_capabilities" says "get": a word for reading.
Description, as the server wrote it Returns the supported question types, the plain-text format reference and plan limits. Call this once before drafting a survey.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Get SurveysAI capabilities
get_profileReturns the signed-in user's stable pseudonymous id, name and email.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_profile" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "return" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it Returns the signed-in user's stable pseudonymous id, name and email.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Get SurveysAI profile
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:21 UTC, unchanged since Nov 10, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.for-google-forms.surveysai.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://for-google-forms.surveysai.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.for-google-forms.surveysai.com/mcp: tools/list returned 6 tools to an anonymous client, including parse_form (write), validate_form (write), create_google_form (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnvalidate_form
The server marks "validate_form" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "validate_form" says "validate": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http for-google-forms https://mcp.for-google-forms.surveysai.com/mcpclaude mcp add --transport http for-google-forms https://mcp.for-google-forms.surveysai.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__for-google-forms__get_capabilities",
"mcp__for-google-forms__get_profile",
"mcp__for-google-forms__get_account_status"
],
"ask": [
"mcp__for-google-forms__parse_form",
"mcp__for-google-forms__validate_form",
"mcp__for-google-forms__create_google_form"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as for-google-forms. Review it before you use it.
Capability tags behind 2 rules
- mcp__for-google-forms__create_google_form untrusted-input
- mcp__for-google-forms__get_profile private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.surveysai/for-google-forms/verify?hash=9dfb7a7300c5e4fcce84f4591658e829392478998551865c6ade81b58bd1805c" | jq -e '.changed == false'Pinned hash 9dfb7a7300c5, from Nov 9, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.surveysai/for-google-forms/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.surveysai/for-google-forms)Source: MCP Registry. Synced Nov 9, 2026, 17:17 UTC.
SurveysAI – Survey Builder for Google Forms MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SurveysAI – Survey Builder for Google Forms MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the SurveysAI – Survey Builder for Google Forms MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the SurveysAI – Survey Builder for Google Forms MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the SurveysAI – Survey Builder for Google Forms MCP server have?
- 6 tools: 3 write, 3 read. parse_form, validate_form, create_google_form, get_capabilities, get_profile and get_account_status.
Does the SurveysAI – Survey Builder for Google Forms MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the SurveysAI – Survey Builder for Google Forms MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the SurveysAI – Survey Builder for Google Forms MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.