Google Forms MCP Server
@matthewwolff/google-forms-mcp
npm
v1.0.2
Source verified
Published by matthewwolff — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Comprehensive MCP server for the Google Forms API — full coverage of form creation, management, responses, and built-in analytics
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Shell/command execution in server code (dist/get-refresh-token.js)MTC-SRC-002
In the server's implementation (`dist/get-refresh-token.js:4`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { execFileSync } from 'child_process'; const CLIENT_ID = process.env.GOOGLE_CLIENT_ID; const CLIENT_SECRET = process.en
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/get-refresh-token.js
Tools 27
Each tool and what it can reach — statically extracted from the published source.
get_responses_tableingests untrusted inputadd_questionno sensitive capabilityadd_sectionno sensitive capabilityadd_text_itemno sensitive capabilityanalyze_frequencyno sensitive capabilitybuild_formno sensitive capabilityclone_formno sensitive capabilitycreate_formno sensitive capabilitycreate_watchno sensitive capabilitycross_tabulateno sensitive capability
Show 17 more tools ↓
delete_formno sensitive capabilitydelete_itemno sensitive capabilitydelete_watchno sensitive capabilityexport_responses_csvno sensitive capabilitygenerate_sankey_datano sensitive capabilityget_formno sensitive capabilityget_form_summaryno sensitive capabilityget_responseno sensitive capabilitylist_formsno sensitive capabilitylist_responsesno sensitive capabilitylist_watchesno sensitive capabilitymove_itemno sensitive capabilityrenew_watchno sensitive capabilityresponse_summaryno sensitive capabilityupdate_form_infono sensitive capabilityupdate_form_settingsno sensitive capabilityupdate_itemno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (27 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.2 latest |
A 94/100 | 1 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @matthewwolff/google-forms-mcp --onlineMore in API Development
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.