stats-compass-mcp@0.3.37
VERIFIED· install onlyPublisher claims: "MCP server exposing stats-compass-core tools to LLMs like ChatGPT, Claude, and Gemini" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 8 of 14 bundled scripts run with no arguments (the rest were not run: per-bundle cap), with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
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
STATS_COMPASS_AUTH_TOKENSTATS_COMPASS_SECRET_KEYor--no-auth/--auth-tokenConfiguration, not credentials: LOCAL_STORAGE_PATH, S3_BUCKET, S3_ENDPOINT_URL, S3_PREFIX, S3_REGION, STATS_COMPASS_DOWNLOAD_TTL_SECONDS, STATS_COMPASS_EXPORTS_DIR, STATS_COMPASS_LOG_FILE, STATS_COMPASS_MAX_SESSIONS, STATS_COMPASS_MAX_UPLOAD_MB, STATS_COMPASS_MEMORY_LIMIT_MB, STATS_COMPASS_SERVER_URL, STORAGE_BACKEND- 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
- use of the skill by an agent
Connect it with a scoped credential, under the guard. It asks for STATS_COMPASS_AUTH_TOKEN, STATS_COMPASS_SECRET_KEY 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.
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; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-18 and scored it 93/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; 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 · 1 s · 2 scenarios · 0 deviationsStatic findings
from stats_compass_mcp.server import create_mcp_server, run_http, run_stdioFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.No other findings across 4,582 lines in 22 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for stats-compass-mcp@0.3.37 as of 6 h ago. This is the package itself, not its dependencies.