MCP Registry

@toolsdk.ai/google-analytics-mcp

by seeygo
17a5bd9e-5ce5-5955-8550-124b5cdb8292 | Store v1.0.5
60/ 100
MEDIUM risk
Risk verdict
Review before use

Score-based assessment (medium risk, 60/100). An AI review is available in the AI review tab.

Analysis record

Analysed
7 months ago 18 April 2026
Version
v1.0.5
Artifact
SHA256 17f18176…53f5e3
Detail
Full list

Evidence ledger

Ranked by severity · findings with a source location link to the code viewer

14 findings

YARA Rule Matches

4 rules
SeverityRuleHitsFilesMetadata
HIGHpostinstall file download

File download activity detected

2
src/index.jsREADME.md
Risky Plugins Authors FP 30%
HIGHcredential env files

Environment configuration file path detected

2
src/index.jsREADME.md
Risky Plugins Authors FP 10%
HIGHpostinstall network communication

Network communication detected

2
LICENSEsrc/index.js
Risky Plugins Authors FP 30%
HIGHpostinstall system command

System command execution detected

2
src/index.jsREADME.md
Risky Plugins Authors FP 10%

Finding Categories

8
Malware Signatures
2
Secrets
13
IoC Indicators

YARA Rules Matched

4 rules(8 hits)
postinstall file download credential env files postinstall network communication postinstall system command

MCP Server Analysis

MCP servers expose tools and resources to AI assistants. Unlike browser extensions, they run as standalone processes with direct system access. Tool definitions are analyzed for prompt injection, data exfiltration, and tool poisoning patterns.

AI Security Report

AI Security Review

Evidence context: threat category none; evidence quality weak.

This package appears to be a standard Model Context Protocol (MCP) server for integrating Google Analytics. The elevated risk score (81.64) is primarily driven by a high volume of Indicator of Compromise (IoC) findings (16 total) and malware-signature matches (8 total) classified as 'high' and 'medium' severity.

Upon closer inspection of the threat model for MCP servers, these findings are characteristic of false positives common in bundled JavaScript dependencies:

  1. No Tool Poisoning: The most critical threat for MCP packages—hidden instructions in tool descriptions—is completely absent (0 findings). This is a strong positive signal.
  2. No Exfiltration Architecture: While the server may legitimately use a Google API key (environment variable access), there are no 'secret' or 'credential-access' findings combined with 'network' findings to an unknown domain, which would indicate data theft. The lack of network findings suggests the scanner may have missed the actual Google API calls or they were not flagged, but the absence of unknown network calls rules out exfiltration.
  3. IoC and Signature Noise: The 'malware-signature' hits and IoCs are likely artifacts from minified code within node_modules or the dist folder. Generic YARA rules often misidentify standard library code or configuration strings as malicious when stripped of context.

Given the lack of malicious intent signals and the presence of benign SDK patterns, the package is likely safe for use but requires standard due diligence regarding API key permissions.

Key Reasons

  • Zero tool poisoning findings detected (ruling out the primary MCP threat vector)
  • No network findings detected to external non-Google domains (rules out exfiltration)
  • High risk score driven entirely by generic IoC and malware-signature rules prone to false positives in dist/ bundles
  • No credential-access findings targeting sensitive local files (e.g., .aws, .ssh)

False Positive Considerations

  • Malware signatures and IoCs triggered by bundled/minified dependencies in dist/ or node_modules/
  • Generic YARA rules matching hex patterns or strings in library code

Reviewed 2026-04-13; recommended action: suppress false positive; model confidence 82%.

Source Code Viewer

Source Code Not Available

Source code is not available for this version of the extension.

About This Extension

MCP server for Google Analytics Data API

Frequently Asked Questions