# hum (mcpb · hum.mcpb)

Free music for your coding agent. Play songs, mood stations and Spotify links in your browser.

- Trust score: 44/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-06

## Components

- mcpb · `hum.mcpb`: 44/100 (this document), [markdown](https://verifymcp.io/servers/anzal1-hum/hum.md), [page](https://verifymcp.io/servers/anzal1-hum/hum)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/anzal1/hum/releases/download/v0.2.1/hum.mcpb`
- Transport: `stdio`
- SHA-256: `db24475f57ed230460514d6120adff178557ca6cfdf3118c47fb15d5e81f7f48`

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

- **Supply Chain Security**: 13/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - No install/post-install scripts declared.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 257 tokens (~42/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

## Install

### How do I install the hum MCP server?

hum ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, db24475f57ed230460514d6120adff178557ca6cfdf3118c47fb15d5e81f7f48; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/anzal1/hum/releases/download/v0.2.1/hum.mcpb`
- SHA-256: `db24475f57ed230460514d6120adff178557ca6cfdf3118c47fb15d5e81f7f48`

### Verify on macOS / Linux

```bash
echo "db24475f57ed230460514d6120adff178557ca6cfdf3118c47fb15d5e81f7f48  hum.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\hum.mcpb).Hash -eq "db24475f57ed230460514d6120adff178557ca6cfdf3118c47fb15d5e81f7f48"
```

## 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-10-02 (score 44)

First indexed and scored.

## MCP tools (6)

### `play` (~56 tokens)

Play a song on hum. Takes any search: a title, an artist, or both ("Blinding Lights", "Kesariya Arijit Singh"). Music keeps going afterwards with similar songs.

Input parameters:

- `query` (string, required): What to play

### `station` (~58 tokens)

Start an endless mix in a mood or around a seed song, for example "lofi beats", "deep focus", "90s bollywood", "Nujabes".

Input parameters:

- `mood` (string, required): A mood, genre, artist or seed song

### `play_playlist` (~32 tokens)

Play a public Spotify playlist, album or track link through hum.

Input parameters:

- `url` (string, required): open.spotify.com link

### `control` (~32 tokens)

Pause, resume, skip to the next song, or go back to the previous one.

Input parameters:

- `action` (string, required)

### `volume` (~24 tokens)

Set the volume from 0 to 100.

Input parameters:

- `level` (number, required)

### `now_playing` (~27 tokens)

What hum is playing right now, the lyric line being sung, and what comes next.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/anzal1-hum/hum#diagnostics

## Score history

- 2026-10-06: 44
- 2026-10-04: 44
- 2026-10-03: 44
- 2026-10-02: 44

## Common questions

### What is the hum MCP server?

hum is an MCP server listed in the public MCP registry as io.github.anzal1/hum. Free music for your coding agent. Play songs, mood stations and Spotify links in your browser. This page covers its MCPB bundle (https://github.com/anzal1/hum/releases/download/v0.2.1/hum.mcpb).

### Is the hum MCP server safe to use?

hum scores 44 out of 100 on VerifyMCP. 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 hum MCP server expose?

hum exposes 6 tools: play, station, play_playlist, control, volume, now_playing. Their descriptions and schemas cost roughly 229 tokens of context every time the server is loaded.

### What licence is the hum MCP server under?

hum declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/anzal1/hum
- Website: https://hum.anzalabidi.dev/
- Changelog RSS feed: https://verifymcp.io/servers/anzal1-hum/hum.xml
- Changelog JSON feed: https://verifymcp.io/servers/anzal1-hum/hum.json
- HTML version of this page: https://verifymcp.io/servers/anzal1-hum/hum