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.
git clone --depth 1 https://github.com/scottie-will/google-tasks-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/scottie-will/google-tasks-mcp/google-tasks-mcp)<a href="https://agentmods.dev/mcp/scottie-will/google-tasks-mcp/google-tasks-mcp"><img src="https://agentmods.dev/badge/mcp/scottie-will/google-tasks-mcp/google-tasks-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/scottie-will/google-tasks-mcp/google-tasks-mcp"><img src="https://agentmods.dev/badge/mcp/scottie-will/google-tasks-mcp/google-tasks-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
google-tasks-mcp 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 8d 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-tasks-mcp": { "command": "npx", "args": [ "-y", "@scottie-will/google-tasks-mcp" ] } }
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.
- 8d ago First seen · 9 lines scan A 33ccd0c6ed5e
google-tasks-mcp is an MCP server published in the GitHub repository scottie-will/google-tasks-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
basecamp-mcp
Model Context Protocol (MCP) server for Basecamp integration. Enables LLMs to interact with Basecamp projects, messages, todos, comments, people, and kanban boards. Runs locally from the basecamp-mcp npm package.
kaiten-mcp
MCP server for Kaiten — 63 tools across cards, comments, checklists, time-tracking, members, blockers, sprints, custom properties, external links, file uploads, location history, and global timesheet. Forked from iamtemazhe/mcp-kaiten with extensive Wave. Runs locally from the kaiten-mcp npm package.
context7
Context7's hosted MCP server: up-to-date library documentation and code examples on demand. Remote server at mcp.context7.com.
toolradar
MCP server for Toolradar — search, compare, and get pricing for 8,600+ software tools. Works with Claude Desktop, Claude Code, Cursor, and any MCP-compatible AI assistant. Runs locally from the toolradar-mcp npm package. Needs 1 environment variable to run.
github-actions
GitHub Actions MCP — view runs, read logs, re-run jobs, and manage CI/CD. Runs locally from the mcp-server-github-actions npm package.
github
Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github npm package.