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/ebmurha/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/ebmurha/google-tasks-mcp/google-tasks-mcp)<a href="https://agentmods.dev/mcp/ebmurha/google-tasks-mcp/google-tasks-mcp"><img src="https://agentmods.dev/badge/mcp/ebmurha/google-tasks-mcp/google-tasks-mcp.svg" alt="Measured on agentmods" 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 7d 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": "uvx",
"args": [
"google-tasks-mcp"
],
"env": {
"GOOGLE_CLIENT_ID": "",
"GOOGLE_CLIENT_SECRET": "",
"GOOGLE_REDIRECT_URI": "",
"DB_PATH": "",
"DEFAULT_TASKLIST": ""
}
}
}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.
- 7d ago First seen · 15 lines scan A d6736451f85a
google-tasks-mcp is an MCP server published in the GitHub repository ebmurha/google-tasks-mcp (2 stars, last pushed 3mo ago), licensed Apache-2.0. 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
smartsuite
MCP server "smartsuite" as configured in SmartSuiteFoundry/smartsuite-mcp-server. Launched with smartsuite-mcp. Needs 4 environment variables to run.
astravue-mcp
Manage projects, tasks, time tracking, and team collaboration through natural language. Remote server at api.astravue.com.
plane-workflow
MCP server "plane-workflow" as configured in amirhosseinkz/plane-workflow-mcp. Runs locally from the plane-workflow Python package.
swsd
MCP server for SolarWinds Service Desk tickets, catalog, knowledge, ITSM operations, and workflows. Runs locally from the swsd-mcp npm package. Needs 5 environment variables to run.
halopsa-mcp
MCP server "halopsa-mcp" as configured in WYRE-AI/halopsa-mcp. Runs in Docker (ghcr.io/wyre-ai/halopsa-mcp:v1.7.13). Needs 7 environment variables to run.
planfix
MCP server for Planfix — tasks, contacts, project management (Russia). Runs locally from the @theyahia/planfix-mcp npm package. Needs 2 environment variables to run.