Analytics (mcp-analytics) MCP Server
@mcp-analytics/mcp-analytics
npm
v1.0.0
Published by @mcp-analytics — 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.
MCP server for statistical analysis, forecasting, and ML. Connects to MCP Analytics API for interactive HTML reports.
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
critical Completed toxic-flow trifecta across toolsMTC-FLOW-002
This server (without client built-ins) exposes a complete data-exfiltration chain: datasets_download → datasets_read → datasets_upload. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.
Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.
Location: flow datasets_download → datasets_read → datasets_upload
Tools 19
Each tool and what it can reach — statically extracted from the published source.
datasets_downloadingests untrusted inputdatasets_readreads sensitive datadatasets_uploadnetwork egressaboutno sensitive capabilityagent_advisorno sensitive capabilitybillingno sensitive capabilityconnectors_listno sensitive capabilityconnectors_queryno sensitive capabilitydatasets_listno sensitive capabilitydatasets_updateno sensitive capability
Show 9 more tools ↓
discover_toolsno sensitive capabilitymodule_requestno sensitive capabilityreport_cardsno sensitive capabilityreports_listno sensitive capabilityreports_searchno sensitive capabilityreports_viewno sensitive capabilitytools_infono sensitive capabilitytools_runno sensitive capabilitytools_schemano sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (19 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 1
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 |
|---|---|---|---|---|
v1.0.0 latest |
A 93/100 | 1 | 1.13.0 | 2026-08-30 |
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 @mcp-analytics/mcp-analytics --onlineOther implementations of Analytics 6
Independent packages implementing the same tool, scanned with the same engine. Compare all 7 side by side →
MCP analytics wrapper SDK that instruments MCP tool declarations with telemetry.
Amplitude MCP Analytics SDK - MCP server usage tracking for Amplitude Analytics
A Model Context Protocol server for analytical queries on the freispace platform.
AIWerk Analytics MCP server — read-only website traffic + Search Console data via share tokens
MCP server for Google Analytics
Security scan results for the Analytics (npm) MCP server.
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
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.
MCP Server for Microsoft Clarity based on data export API