io.github.CloudCorpRecords/musicport
NPM · @RENETURCIOS/MUSICPORT · 2 COMPONENTS
Spotify search, playback and playlists as MCP tools.
Available components
Last scanned (13 hours ago)
Scores higher than 32% of npm servers
Category Entertainment and Games
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 409 tokens (~34/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 49
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@reneturcios/musicport@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_tracks_to_playlist ~56
Add tracks to a Spotify playlist.
| Name | Type | Req | Description |
|---|---|---|---|
| playlist_id | string | yes | The unique identifier of the Spotify playlist to add tracks to. |
| uris | array | yes | The list of Spotify track URIs to add to the playlist. |
No output schema declared.
No examples provided.
create_playlist ~60
Create a Spotify playlist for the current user.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional description for the new playlist. |
| name | string | yes | The name to give the new playlist. |
| public | boolean | – | Optional flag indicating whether the new playlist is public. |
No output schema declared.
No examples provided.
get_current_user_profile ~17
Get the current Spotify user's profile.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_playback_state ~17
Get the current Spotify playback state.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_playlist ~32
Retrieve a Spotify playlist by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| playlist_id | string | yes | The unique identifier of the Spotify playlist to retrieve. |
No output schema declared.
No examples provided.
list_playlists ~30
List the current user's Spotify playlists.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Optional maximum number of playlists to return. |
No output schema declared.
No examples provided.
list_saved_tracks ~32
List the current user's saved Spotify tracks.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Optional maximum number of saved tracks to return. |
No output schema declared.
No examples provided.
next_track ~15
Skip to the next Spotify track.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pause ~11
Pause Spotify playback.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
play ~54
Start or resume Spotify playback.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Optional identifier of the device to start playback on. |
| uris | array | – | Optional list of Spotify URIs to play; omitted from the request when not provided. |
No output schema declared.
No examples provided.
previous_track ~15
Skip to the previous Spotify track.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search ~70
Search Spotify catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Optional maximum number of search results to return. |
| query | string | yes | The search text to query the Spotify catalog with, sent as the q parameter. |
| type | string | – | Optional type of item to search for (defaults to 'track' when omitted). |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/musicport MCP server?
io.github.CloudCorpRecords/musicport runs locally as an npm package, launched with npx -y @reneturcios/musicport mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/musicport
claude mcp add cloudcorprecords-musicport -- npx -y @reneturcios/musicport mcp
What is the io.github.CloudCorpRecords/musicport MCP server?
io.github.CloudCorpRecords/musicport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/musicport. Spotify search, playback and playlists as MCP tools. This page covers its npm package (@reneturcios/musicport).
Is the io.github.CloudCorpRecords/musicport MCP server safe to use?
io.github.CloudCorpRecords/musicport scores 64 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.CloudCorpRecords/musicport MCP server expose?
io.github.CloudCorpRecords/musicport exposes 12 tools: search, get_current_user_profile, get_playback_state, play, pause, and 7 more. Their descriptions and schemas cost roughly 409 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/musicport MCP server still maintained?
io.github.CloudCorpRecords/musicport is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.CloudCorpRecords/musicport MCP server under?
io.github.CloudCorpRecords/musicport declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.CloudCorpRecords/musicport MCP server?
VerifyMCP ran 15 checks on io.github.CloudCorpRecords/musicport, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/musicport: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.