# io.github.tothienbao6a0/upnext (npm · upnext-mcp)

One audio queue across Spotify, the browser, local files and whatever is already playing.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `upnext-mcp`: 78/100 (this document), [markdown](https://verifymcp.io/servers/tothienbao6a0-upnext/upnext-mcp.md), [page](https://verifymcp.io/servers/tothienbao6a0-upnext/upnext-mcp)

## Channel facts

- Registry: `npm`
- Package: `upnext-mcp`
- Version: `0.3.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 10 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 20 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 406 tokens (~33/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 33% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add tothienbao6a0-upnext -- npx -y upnext-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "tothienbao6a0-upnext": {
      "command": "npx",
      "args": [
        "-y",
        "upnext-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tothienbao6a0-upnext": {
      "command": "npx",
      "args": [
        "-y",
        "upnext-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add tothienbao6a0-upnext -- npx -y upnext-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tothienbao6a0-upnext": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "upnext-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tothienbao6a0-upnext --command npx --arg -y --arg upnext-mcp
```

### Hermes

```yaml
mcp_servers:
  tothienbao6a0-upnext:
    command: "npx"
    args: ["-y", "upnext-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "tothienbao6a0-upnext": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "upnext-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add tothienbao6a0-upnext -t stdio -c npx -a -y upnext-mcp
```

### Other

```json
{
  "mcpServers": {
    "tothienbao6a0-upnext": {
      "command": "npx",
      "args": [
        "-y",
        "upnext-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 78, +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.

### 2026-09-18 (score 77, +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.

### 2026-09-16 (score 76, +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.

### 2026-09-14 (score 75, +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.

### 2026-09-11 (score 74, +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.

### 2026-09-09 (score 73, +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.

### 2026-09-07 (score 72, +4)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-01 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (12)

### `media_now` (~30 tokens)

What is playing right now — including audio this machine is playing outside the queue, such as a browser tab.

### `media_queue` (~19 tokens)

Show the queue, with the id of each entry.

### `media_enqueue` (~75 tokens)

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.

Input parameters:

- `item` (string, required): A link, a file path, a spotify: URI, or a description
- `position` (string)

### `media_play` (~38 tokens)

Start or resume playback. With an id, plays that entry now. With nothing, resumes or starts the queue.

Input parameters:

- `id` (string)

### `media_pause` (~11 tokens)

Pause playback.

### `media_next` (~14 tokens)

Skip to the next entry.

### `media_seek` (~32 tokens)

Jump to a position in the current track. Fails if the backend cannot seek.

Input parameters:

- `seconds` (number, required)

### `media_move` (~49 tokens)

Reorder the queue. Both ids come from media_queue.

Input parameters:

- `after` (string): put it after this entry; omit to put it next
- `id` (string, required): the entry to move

### `media_remove` (~25 tokens)

Remove an entry from the queue, by id.

Input parameters:

- `id` (string, required)

### `media_search` (~41 tokens)

Search the sources that can search. Returns ids you can pass to media_enqueue as a uri.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `media_adopt_current` (~42 tokens)

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.

### `media_setup` (~30 tokens)

What audio sources are wired here, and what they can do — including whether a plain description can be resolved.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/tothienbao6a0-upnext/upnext-mcp#diagnostics

## Score history

- 2026-09-21: 78
- 2026-09-20: 78
- 2026-09-19: 77
- 2026-09-18: 77
- 2026-09-17: 76
- 2026-09-16: 76
- 2026-09-15: 75
- 2026-09-14: 75
- 2026-09-13: 74
- 2026-09-12: 74
- 2026-09-11: 74
- 2026-09-10: 73
- 2026-09-09: 73
- 2026-09-08: 72
- 2026-09-07: 72
- 2026-09-06: 68
- 2026-09-05: 68
- 2026-09-04: 68
- 2026-09-03: 68
- 2026-09-02: 68
- 2026-09-01: 68
- 2026-08-31: 53

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/upnext-mcp
- Socket report: https://socket.dev/npm/package/upnext-mcp
- Repository: https://github.com/tothienbao6a0/upnext
- Changelog RSS feed: https://verifymcp.io/servers/tothienbao6a0-upnext/upnext-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tothienbao6a0-upnext/upnext-mcp.json
- HTML version of this page: https://verifymcp.io/servers/tothienbao6a0-upnext/upnext-mcp