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/getmcpads-com/google-analytics-mcp-server/google-analyticsgit clone --depth 1 https://github.com/getmcpads-com/google-analytics-mcp-serverWrote 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/getmcpads-com/google-analytics-mcp-server/google-analytics)<a href="https://agentmods.dev/mcp/getmcpads-com/google-analytics-mcp-server/google-analytics"><img src="https://agentmods.dev/badge/mcp/getmcpads-com/google-analytics-mcp-server/google-analytics.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
google-analytics 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 2d 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-analytics": {
"command": "npx",
"args": [
"-y",
"@getmcpads/google-analytics-mcp-server"
],
"env": {
"GA4_CLIENT_ID": "",
"GA4_CLIENT_SECRET": "",
"GA4_REFRESH_TOKEN": "",
"GA4_PROPERTY_ID": ""
}
}
}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.
- 2d ago First seen · 15 lines scan A 9399b42a6783
google-analytics is an MCP server published in the GitHub repository getmcpads-com/google-analytics-mcp-server (0 stars, last pushed 4d 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
google-analytics-mcp
Model Context Protocol for Google Analytics 4 (Data API) allowing autonomous agents to query dimensions and metrics. Gives agents analysis-ready GA4 access with schema discovery, server-side aggregation, and smart defaults. Runs locally from the google-analytics-mcp Python package. Needs 2 environment variables to run.
adloop
MCP server "adloop" as configured in kLOsk/adloop. Runs locally from the . Python package.
google_analytics
MCP server "googleanalytics" as configured in powehi-eu/google-suite-seo-mcp. Launched with analytics-mcp. Needs 2 environment variables to run.
mcp-google-analytics
GA4 MCP that reads AND writes: reports, funnels, audits, and server-side events. 26 tools. Runs locally from the mcp-google-analytics npm package. Needs 4 environment variables to run.
google_search_console
MCP server "googlesearchconsole" as configured in powehi-eu/google-suite-seo-mcp. Launched with gsc-mcp. Needs 1 environment variable to run.
google-analytics
GA4 MCP server that reads AND writes: run reports and funnels (Data API), audit your setup (custom dimensions, key events, compatibility checks), and send events server-side (Measurement Protocol v2). Runs locally from the mcp-google-analytics npm package. Needs 2 environment variables to run.