Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/naster3/google-forms-mcp/google-forms-mcp-nastergit clone --depth 1 https://github.com/naster3/google-forms-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/naster3/google-forms-mcp/google-forms-mcp-naster)<a href="https://agentmods.dev/mcp/naster3/google-forms-mcp/google-forms-mcp-naster"><img src="https://agentmods.dev/badge/mcp/naster3/google-forms-mcp/google-forms-mcp-naster.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
google-forms-mcp-naster scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "google-forms-mcp-naster": { "command": "npx", "args": [ "-y", "google-forms-mcp-naster" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 9 lines scan A 3517755db20b
google-forms-mcp-naster is an MCP server published in the GitHub repository naster3/google-forms-mcp (0 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp-server-google-forms
Cria, edita e publica Google Forms a partir do Claude: quizzes, seções e leitura de respostas. Runs locally from the mcp-server-google-forms npm package. Needs 1 environment variable to run.
google-forms-mcp
MCP server "google-forms-mcp" as configured in xari-ya/google-forms-mcp-extended. Runs locally from the google-forms-mcp Python package.
mcp
MCP server "mcp" as configured in formswrite/formswrite-mcp. Runs locally from the @formswrite/mcp npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.