spotify-analytics-mcp@0.2.0
VERIFIED· not startedPublisher claims: "MCP server and CLI installer for the Spotify AI Analytics project." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
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
TOKEN_ENCRYPT_KEYConfiguration, not credentials: SPOTIFY_CLIENT_ID, SPOTIFY_USER_ID- Where it talks to
- no vendor host named in the codeAlso spotify.com, langfuse.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names spotify.com, langfuse.com as well as its own vendor. The guard injects TOKEN_ENCRYPT_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
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; not started: dependency install failed; the server itself was not observed) on 2026-11-18 and scored it 84/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 · 0 s · 2 scenarios · 0 deviationsStatic findings
return all(importlib.util.find_spec(name) is not None for name in _DASHBOARD_IMPORTS)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""Prefer process env, fall back to <config_dir>/.env."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# platform .env via pydantic-settings; get_client_id/get_fernet_key delegate to it.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Load platformdirs .env first; cwd .env fills any gaps but never overrides.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Bridge the platform .env into os.environ so env-based SDKs (e.g. Langfuse) seeFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.print("[dim]Skipped LLM setup. You can add keys to .env later.[/dim]")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Load the platform .env into os.environ so env-based SDKs (e.g. Langfuse) seeFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.logger.warning("SPOTIFY_CLIENT_ID is not set. Set it in .env or as an environment variable.")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.typer.Option("--user-id", help="Spotify user ID (defaults to SPOTIFY_USER_ID from .env)"),Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# their credentials. The cwd .env is a dev-checkout fallback (no override).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
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 spotify-analytics-mcp@0.2.0 as of 9 h ago. This is the package itself, not its dependencies.