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/claude-book/mcp-server-google-forms/mcp-server-google-formsgit clone --depth 1 https://github.com/claude-book/mcp-server-google-formsWrote 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/claude-book/mcp-server-google-forms/mcp-server-google-forms)<a href="https://agentmods.dev/mcp/claude-book/mcp-server-google-forms/mcp-server-google-forms"><img src="https://agentmods.dev/badge/mcp/claude-book/mcp-server-google-forms/mcp-server-google-forms.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-server-google-forms 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 5d 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
{
"mcp-server-google-forms": {
"command": "npx",
"args": [
"-y",
"mcp-server-google-forms"
],
"env": {
"GOOGLE_FORMS_MCP_DIR": ""
}
}
}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.
- 5d ago First seen · 12 lines scan A 9e0ec6605079
mcp-server-google-forms is an MCP server published in the GitHub repository claude-book/mcp-server-google-forms (0 stars, last pushed 28d 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
anytype-mcp
Official MCP server for Anytype API - your encrypted, local and collaborative wiki. Runs locally from the @anyproto/anytype-mcp npm package. Needs 1 environment variable to run.
notion-mcp-server
Token-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents. Runs locally from the notion-mcp-server npm package. Needs 2 environment variables to run.
joplin-mcp
Model Context Protocol (MCP) server for Joplin note-taking application. Runs locally from the joplin-mcp Python package. Needs 2 environment variables to run.
caldav-mcp
CalDAV calendar operations (list, create, update, delete events) as MCP tools. Runs locally from the caldav-mcp npm package. Needs 3 environment variables to run.
mcp-telegram
MCP server for Telegram userbot — messages, media, reactions, polls & more. Built on GramJS/MTProto. Runs locally from the @overpod/mcp-telegram npm package. Needs 2 environment variables to run.
workflowy
MCP server "workflowy" as configured in mholzen/workflowy. Runs in Docker (ghcr.io/mholzen/workflowy:0.8.1). Needs 1 environment variable to run.