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/ftaricano/mcp-gmail-calendarWrote 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/ftaricano/mcp-gmail-calendar/gmail-calendar)<a href="https://agentmods.dev/mcp/ftaricano/mcp-gmail-calendar/gmail-calendar"><img src="https://agentmods.dev/badge/mcp/ftaricano/mcp-gmail-calendar/gmail-calendar/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/ftaricano/mcp-gmail-calendar/gmail-calendar"><img src="https://agentmods.dev/badge/mcp/ftaricano/mcp-gmail-calendar/gmail-calendar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gmail-calendar 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 9d 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
{ "gmail-calendar": { "command": "npx", "args": [ "-y", "@mcp/gmail-calendar" ] } }
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.
- 9d ago First seen · 9 lines scan A 9454ad2e9e5a
gmail-calendar is an MCP server published in the GitHub repository ftaricano/mcp-gmail-calendar (0 stars, last pushed 1mo 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
gws-mcp-server
Google Workspace as 39 curated MCP tools: Gmail, Calendar, Drive, Sheets, Docs, and Tasks. Runs locally from the gws-mcp-server npm package.
mcp-google-workspace
MCP Server to connect to Google Workspace (Gmail & Calendar). Runs locally from the mcp-google-workspace Python package.
google-accounts-mcp
Multi-account Google MCP server: Gmail, Calendar, Drive, Tasks, and Contacts. Runs locally from the google-accounts-mcp Python package.
claude-2-mail
MCP server "claude-2-mail" as configured in omkargs/claude-2-mail. Runs locally from the claude-2-mail Python package.
personal-gmail-mcp
Model Context Protocol server for a personal Gmail (consumer Google account) inbox and calendar, via the Gmail and Google Calendar APIs. Stdio transport, loopback OAuth, OS-keyring token cache. Runs locally from the @jaingxyz/personal-gmail-mcp npm package.
sap-gui
MCP server "sap-gui" as configured in kts982/mcp-sap-gui. Runs locally from the python Python package.