Skills/npm/zoho-analytics-mcp-server

zoho-analytics-mcp-server@1.0.7

VERIFIED· startup only

Publisher claims: "MCP server implementation for Zoho Analytics" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher zoho-corp · publishing for 416 daysInstalls 688Last detonated 3d ago
$claude mcp add zoho-analytics-mcp-server -- npx -y zoho-analytics-mcp-server
WatchReport an issue

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
ANALYTICS_CLIENT_SECRET, ANALYTICS_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
ANALYTICS_CLIENT_SECRETANALYTICS_REFRESH_TOKENConfiguration, not credentials: ACCOUNTS_SERVER_URL, ALLOWED_FILE_ROOT, ANALYTICS_CLIENT_ID, ANALYTICS_ORG_ID, ANALYTICS_SERVER_URL, DEBUG_PORT, PRODUCT_NAME, QUERY_DATA_RESULT_ROW_LIMITS
Where it talks to
no vendor host named in the code
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 ANALYTICS_CLIENT_SECRET, ANALYTICS_REFRESH_TOKEN and talks to its vendor. 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.

$vet-skills run --net declared -- npx -y zoho-analytics-mcp-server

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-11 and scored it 95/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 ANALYTICS_CLIENT_SECRET, ANALYTICS_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 · 48 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
7.3sprocessdependency install exit 0
27sprocessrelaunched with a decoy ANALYTICS_CLIENT_SECRET, ANALYTICS_REFRESH_TOKEN (tagged; nothing real)
47sclaimedstartup only: exited before answering, asking for ANALYTICS_CLIENT_SECRET, ANALYTICS_REFRESH_TOKEN (a decoy value was refused)
47sprocessscript backend runs setup only
47sprocessno install scripts to re-run

Static findings

No findings across 8,782 lines in 32 files.

Cost to the agent

Instructions loaded
≈53 tok
1 file · 32 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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 zoho-analytics-mcp-server@1.0.7 as of 3d ago. This is the package itself, not its dependencies.