Google Analytics (surendranb) MCP Server
google-analytics-mcp
PyPI
v2.11.3
Published by surendranb — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
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.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Shell/command execution in server code (ga4_mcp/telemetry.py)MTC-SRC-002
In the server's implementation (`ga4_mcp/telemetry.py:211`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: break out = subprocess.check_output( ["ps", "-p", str(pid), "-o", "ppid=,comm="], text=True,
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server ga4_mcp/telemetry.py
Tools 9
Each tool and what it can reach — statically extracted from the published source.
list_dimension_categoriesingests untrusted inputlist_metric_categoriesingests untrusted inputsearch_schemaingests untrusted inputsearch_skillsingests untrusted inputget_dimensions_by_categoryno sensitive capabilityget_ga4_datano sensitive capabilityget_metrics_by_categoryno sensitive capabilityget_property_schemano sensitive capabilityget_troubleshooting_guideno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (9 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 8
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.11.3 latest |
A 93/100 | 1 | 1.13.0 | 2026-08-25 |
v2.11.1 |
A 93/100 | 1 | 1.12.1 | 2026-08-16 |
v2.11.0 |
A 93/100 | 1 | 1.12.1 | 2026-08-12 |
v2.10.0 |
A 93/100 | 1 | 1.12.1 | 2026-08-10 |
v2.9.0 |
A 93/100 | 1 | 1.12.1 | 2026-08-02 |
Show 3 more versions ↓
v2.8.4 |
A 93/100 | 1 | 1.12.1 | 2026-07-31 |
v2.8.3 |
A 93/100 | 1 | 1.12.1 | 2026-07-27 |
v2.8.1 |
A 93/100 | 1 | 1.9.0 | 2026-07-23 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan google-analytics-mcp --online --registry pypiOther implementations of Google Analytics 5
Independent packages implementing the same tool, scanned with the same engine. Compare all 6 side by side →
MCP server for Google Analytics Data API and Measurement Protocol - Read reports and send events
MCP server for Google Analytics Data API
Google Analytics MCP Pack
Google Analytics MCP server for accessing web analytics data
Model Context Protocol server for Google Analytics - query reports, manage properties, configure data filters, and analyze website performance
More in Analytics & Monitoring
Public-safe MCP admin discovery contract descriptors and response builders.
Pokemon Champions battle advisor MCP server
Airflow MCP server — DAG list, runs, task instances, log tails, trigger and clear over the Airflow REST API
MCP analytics wrapper SDK that instruments MCP tool declarations with telemetry.
AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
AI-native social listening. Monitor buying signals and run GTM workflows via natural language.