Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Google_analytics

NPM · @PIPEWORX/MCP-GOOGLE_ANALYTICS · 2 COMPONENTS

Google Analytics MCP Pack

+3 this week 83 Trust /100

Last scanned (2 hours ago)

Scores higher than 76% of npm servers

Category Data and Analytics

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-google_analytics). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 571 tokens (~142/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: fail → unverified ▼ functional
  • 2 Nov 26 −13
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.13 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 80

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-google_analytics@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-google_analytics
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-google_analytics/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637331179
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:6fe7f5bcd58bf8592f670344c9f33ed8a49b54eeeff612a416976a7bb98a14690a826fb9cdfb02481b462564affdc57393d70a58d4608a06669e429ff

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~517 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ga_get_metadata ~51

Discover available dimensions and metrics for a GA4 property. Returns field names, descriptions, and data types to build accurate ga_run_report queries.

NameTypeReqDescription
property_idstringyesGA4 property ID (numeric)

No output schema declared.

No examples provided.

ga_get_realtime ~128

Check live user activity in a GA4 property right now. Returns current active user count and real-time engagement metrics. Specify property ID (e.g., "123456789").

NameTypeReqDescription
dimensionsarray–Realtime dimensions (e.g., ["city", "unifiedScreenName", "platform"])
limitnumber–Maximum number of rows (default 100)
metricsarray–Realtime metrics (e.g., ["activeUsers", "screenPageViews"]). Defaults to ["activeUsers"].
property_idstringyesGA4 property ID (numeric)

No output schema declared.

No examples provided.

ga_list_properties ~78

List all GA4 properties you can access. Returns property IDs, names, creation dates, and account info. Use to find the property ID for ga_run_report queries.

NameTypeReqDescription
page_sizenumber–Maximum number of account summaries to return (default 50)
page_tokenstring–Token for fetching the next page of results

No output schema declared.

No examples provided.

ga_run_report ~260

Query GA4 analytics data by dimensions (e.g., "city", "pagePath") and metrics (e.g., "activeUsers", "sessions") for a date range. Returns aggregated data rows with dimension and metric values.

NameTypeReqDescription
dimension_filterobject–Optional dimension filter object (GA4 FilterExpression format)
dimensionsarray–List of dimension names (e.g., ["city", "pagePath", "date"])
end_datestringyesEnd date (YYYY-MM-DD or relative: "today", "yesterday")
limitnumber–Maximum number of rows to return (default 100, max 10000)
metricsarrayyesList of metric names (e.g., ["activeUsers", "sessions", "screenPageViews"])
order_bysarray–Optional ordering. Each item: { dimension: { dimensionName, orderType? } } or { metric: { metricName }, desc? }
property_idstringyesGA4 property ID (numeric, e.g., "123456789")
start_datestringyesStart date (YYYY-MM-DD or relative: "today", "yesterday", "7daysAgo", "30daysAgo")

No output schema declared.

No examples provided.

Install

How do I install the Google_analytics MCP server?

Google_analytics runs locally as an npm package, launched with npx -y @pipeworx/mcp-google_analytics. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-google_analytics

# add to Claude Code
claude mcp add pipeworx-io-google-analytics -- npx -y @pipeworx/mcp-google_analytics
Common questions

What is the Google_analytics MCP server?

Google_analytics is an MCP server listed in the public MCP registry as io.github.pipeworx-io/google_analytics. Google Analytics MCP Pack. This page covers its npm package (@pipeworx/mcp-google_analytics).

Is the Google_analytics MCP server safe to use?

Google_analytics scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Google_analytics MCP server expose?

Google_analytics exposes 4 tools: ga_run_report, ga_list_properties, ga_get_realtime, ga_get_metadata. Their descriptions and schemas cost roughly 517 tokens of context every time the server is loaded.

Is the Google_analytics MCP server still maintained?

Google_analytics is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Google_analytics MCP server under?

Google_analytics declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.