io.github.tothienbao6a0/upnext
NPM · UPNEXT-MCP · SCANNED SEP 21
One audio queue across Spotify, the browser, local files and whatever is already playing.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 10 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- 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 (Apache-2.0).Pass
- Actively maintained (last published 20 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 406 tokens (~33/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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "media_remove" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- 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 current MCP spec version (2026-07-28).Pass
How do I install the io.github.tothienbao6a0/upnext MCP server?
io.github.tothienbao6a0/upnext runs locally as an npm package, launched with npx -y upnext-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 · upnext-mcp
claude mcp add tothienbao6a0-upnext -- npx -y upnext-mcp
{
"mcpServers": {
"tothienbao6a0-upnext": {
"command": "npx",
"args": [
"-y",
"upnext-mcp"
]
}
}
} {
"servers": {
"tothienbao6a0-upnext": {
"command": "npx",
"args": [
"-y",
"upnext-mcp"
]
}
}
} codex mcp add tothienbao6a0-upnext -- npx -y upnext-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tothienbao6a0-upnext": {
"type": "local",
"command": [
"npx",
"-y",
"upnext-mcp"
],
"enabled": true
}
}
} openclaw mcp add tothienbao6a0-upnext --command npx --arg -y --arg upnext-mcp
mcp_servers:
tothienbao6a0-upnext:
command: "npx"
args: ["-y", "upnext-mcp"] {
"McpServers": {
"tothienbao6a0-upnext": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"upnext-mcp"
]
}
}
} assistant mcp add tothienbao6a0-upnext -t stdio -c npx -a -y upnext-mcp
{
"mcpServers": {
"tothienbao6a0-upnext": {
"command": "npx",
"args": [
"-y",
"upnext-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +4
- Stability: unverified → 0.23 ▲ functional
- 1 Sept 26 +15
- Malware scan: unverified → pass ▲ security
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 21 Sept 2026 · Analysed npm/upnext-mcp@0.3.1
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 →
Dependencies 10 packages
| Packages resolved | 10 |
|---|---|
| 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 →
media_adopt_current ~42
Put whatever this machine is already playing — a browser tab, another app — into the queue, so your entries start when it finishes instead of cutting across it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
media_enqueue ~75
Add something to the queue. Accepts a link, a file path, a Spotify URI, or a plain description to be resolved later. Use position to play it next rather than last.
| Name | Type | Req | Description |
|---|---|---|---|
| item | string | yes | A link, a file path, a spotify: URI, or a description |
| position | string | – | – |
No output schema declared.
No examples provided.
media_move ~49
Reorder the queue. Both ids come from media_queue.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | put it after this entry; omit to put it next |
| id | string | yes | the entry to move |
No output schema declared.
No examples provided.
media_next ~14
Skip to the next entry.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
media_now ~30
What is playing right now — including audio this machine is playing outside the queue, such as a browser tab.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
media_pause ~11
Pause playback.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
media_play ~38
Start or resume playback. With an id, plays that entry now. With nothing, resumes or starts the queue.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | – |
No output schema declared.
No examples provided.
media_queue ~19
Show the queue, with the id of each entry.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
media_remove ~25
Remove an entry from the queue, by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
media_search ~41
Search the sources that can search. Returns ids you can pass to media_enqueue as a uri.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
media_seek ~32
Jump to a position in the current track. Fails if the backend cannot seek.
| Name | Type | Req | Description |
|---|---|---|---|
| seconds | number | yes | – |
No output schema declared.
No examples provided.
media_setup ~30
What audio sources are wired here, and what they can do — including whether a plain description can be resolved.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.tothienbao6a0/upnext MCP server?
io.github.tothienbao6a0/upnext is an MCP server listed in the public MCP registry as io.github.tothienbao6a0/upnext. One audio queue across Spotify, the browser, local files and whatever is already playing. This page covers its npm package (upnext-mcp).
Is the io.github.tothienbao6a0/upnext MCP server safe to use?
io.github.tothienbao6a0/upnext scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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.tothienbao6a0/upnext MCP server expose?
io.github.tothienbao6a0/upnext exposes 12 tools: media_now, media_queue, media_enqueue, media_play, media_pause, and 7 more. Their descriptions and schemas cost roughly 406 tokens of context every time the server is loaded.
Is the io.github.tothienbao6a0/upnext MCP server still maintained?
io.github.tothienbao6a0/upnext is still listed as active in the MCP registry. We last reached this channel on 21 September 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.tothienbao6a0/upnext MCP server under?
io.github.tothienbao6a0/upnext declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.