Loading the registry…
A Model Context Protocol (MCP) server for Spotify Web API integration
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
1 critical finding reported by cisco-skill-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- spotify-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
7 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.4s
v2.0.11
12 findings · 6.2s
v0.3.74
11 findings · 1.0s
v0.1.0
10 findings · 2.9s
v0.1.0
0 findings · 2.9s
v0.71.0
11 findings · 0.2s
v2.3.8
34 findings · 6.5s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.6s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged31 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 78 findings across every scanner that examined this package. None of the 1 finding rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 12 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
6 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/src/auth.ts, /repo/src/index.ts, /repo/test-api.ts · reported by nerlo-behavioral
4 opt.nerlo-rules.nerlo-hardcoded-external-egress
Files: /repo/src/auth.ts, /repo/test-api.ts · reported by nerlo-behavioral
2 AAK-ANTHROPIC-SDK-001
Files: test-client.ts, src/index.ts · reported by agent-audit-kit
2 AAK-OAUTH-006
Files: src/auth.ts, src/index.ts · reported by agent-audit-kit
2 AAK-OAUTH-007
Files: src/auth.ts, src/index.ts · reported by agent-audit-kit
2 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-f886-m6hf-6m8v
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json · reported by osv-scanner
1 AAK-DNS-REBIND-002
Files: package.json · reported by agent-audit-kit
1 AAK-MCP-SSRF-001
Files: src/index.ts · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2025-13466
Files: package-lock.json · reported by trivy
1 CVE-2025-15284
Files: package-lock.json · reported by trivy
1 CVE-2025-66414
Files: package-lock.json · reported by trivy
1 CVE-2025-69873
Files: package-lock.json · reported by trivy
1 CVE-2026-0621
Files: package-lock.json · reported by trivy
1 CVE-2026-12590
Files: package-lock.json · reported by trivy
1 CVE-2026-2391
Files: package-lock.json · reported by trivy
1 CVE-2026-25536
Files: package-lock.json · reported by trivy
1 CVE-2026-4923
Files: package-lock.json · reported by trivy
1 CVE-2026-4926
Files: package-lock.json · reported by trivy
1 CVE-2026-8723
Files: package-lock.json · reported by trivy
1 GHSA-25h7-pfq9-p65f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-27v5-c462-wpq7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-345p-7cg4-v4c7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5p4m-2wfm-xmqj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6rw7-vpxm-498p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8r9q-7v3j-jr4g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-c2c7-rcm5-vvqj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-h67p-54hq-rp68
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j3q9-mxjg-w52f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mh29-5h37-fv8m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q8mj-m7cp-5q26
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-rf6f-7fwh-wjgh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w48q-cv73-mx4w
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w7fw-mjwx-w883
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wqch-xfxh-vrr4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xffm-g5w8-qvg7
Files: /repo/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
12 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: COMMAND_INJECTION_JS_CHILD_PROCESS, FILE_MAGIC_MISMATCH, AAK-SEC-MD-001 and 4 more · Files: /repo/test-client.ts, SECURITY.md, /repo/.prettierrc.json and 4 more · reported by cisco-skill-scanner, agent-audit-kit
Critical command injection and network egress risks identified.
The artifact contains a critical command injection vulnerability in `test-client.ts`, enabling shell execution. It also performs network egress from `src/auth.ts`, `src/index.ts`, and `test-api.ts`, potentially exposing secrets. High-severity findings indicate credential access in `src/token-storage.ts` and several vulnerable dependencies. The Anthropic SDK is used in `src/index.ts` and `test-client.ts`, and a DNS rebind vulnerability is noted in `package.json`.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
Showing 23 of 23; the rest are in the per-scanner reports above.