google-analytics-mcp-server@2.1.2
VERIFIED· startup onlyPublisher claims: "Google Analytics 4 MCP server: 27 read tools, no write tools." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
- Needs
- GA4_CLIENT_SECRET, GA4_REFRESH_TOKEN — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
GA4_CLIENT_SECRETGA4_REFRESH_TOKENConfiguration, not credentials: GA4_CLIENT_ID, GA4_DEFAULT_PROPERTY_ID, GA4_PROPERTY_ID- Where it talks to
- getmcpads.com (its own)
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard. It asks for GA4_CLIENT_SECRET, GA4_REFRESH_TOKEN and talks to getmcpads.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-09 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed (it asks for GA4_CLIENT_SECRET, GA4_REFRESH_TOKEN); the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 52 s · 2 scenarios · 0 deviationsStatic findings
<summary><b>6 resources</b></summary> | URI | Contents | |---|---| | `ga4://manifest` | What this server exposes, and which tool to run first | | `ga4://metricsFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.No other findings across 13,710 lines in 11 files.
Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for @getmcpads/google-analytics-mcp-server@2.1.2 as of 5d ago. This is the package itself, not its dependencies.