# BeatSeek (remote · beatseek.io)

SoundCloud search for DJs and AI agents, with BPM and key measured from the audio.

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

## Components

- remote · `beatseek.io`: 66/100 (this document), [markdown](https://verifymcp.io/servers/levz0r-beatseek/api-mcp.md), [page](https://verifymcp.io/servers/levz0r-beatseek/api-mcp)

## Channel facts

- Endpoint: `https://beatseek.io/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 480 tokens (~120/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 64% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 BeatSeek MCP server?

BeatSeek is a hosted endpoint at https://beatseek.io/api/mcp, so there is nothing to install locally. 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 --transport http levz0r-beatseek 'https://beatseek.io/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "levz0r-beatseek": {
      "url": "https://beatseek.io/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "levz0r-beatseek": {
      "type": "http",
      "url": "https://beatseek.io/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.levz0r-beatseek]
url = "https://beatseek.io/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "levz0r-beatseek": {
      "type": "remote",
      "url": "https://beatseek.io/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add levz0r-beatseek --url 'https://beatseek.io/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  levz0r-beatseek:
    url: "https://beatseek.io/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "levz0r-beatseek": {
      "Transport": "http",
      "Url": "https://beatseek.io/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add levz0r-beatseek -t streamable-http -u 'https://beatseek.io/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "levz0r-beatseek": {
      "type": "http",
      "url": "https://beatseek.io/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-20 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-18 (score 65, +30)

- [security regression] HTTPS: pass → unverified
- [security regression] HSTS header: pass → fail
- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Tool coverage: 64
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good

### 2026-11-07 (score 35)

First indexed and scored.

## MCP tools (4)

### `search_soundcloud` (~167 tokens)

Search SoundCloud

Free-text search of SoundCloud tracks, playlists or albums (e.g. 'melodic techno 2026'). Each result carries BPM and key; prefer values with bpmSource/keySource 'analyzed' (measured from audio) over 'uploader' (tags, often wrong). For a known artist + title, use resolve_track instead.

Input parameters:

- `fromDate` (string): ISO date, e.g. 2026-01-01
- `limit` (integer)
- `maxBpm` (number)
- `minBpm` (number)
- `query` (string, required): Search text
- `sort` (string): 'both' blends recency and popularity
- `toDate` (string): ISO date
- `type` (string)

### `resolve_track` (~92 tokens)

Resolve track

Find the best SoundCloud URL for a known artist + title (e.g. a line from a tracklist). Returns the best match and up to 3 alternates, each with a confidence score in [0, 1]; match is null when nothing fits.

Input parameters:

- `artist` (string): Primary artist; strongly improves accuracy
- `limit` (integer): Candidates to score
- `title` (string, required)

### `analyze_track` (~125 tokens)

Measure BPM and key

Measure BPM and musical key (with Camelot code) from the audio of a SoundCloud track, using a 30-second window starting at `position` ms. BPM is corrected for half/double-time errors using the track's genre. First call takes ~5–15 s; repeat calls are cached for 30 days. Limited to 6 calls per minute per client. Preview snippets (≤60 s) are rejected.

Input parameters:

- `position` (integer): Start of the analysis window in ms; use it for long mixes
- `url` (string, required): SoundCloud track URL

### `get_playlist` (~31 tokens)

Get playlist tracks

List the tracks of a SoundCloud playlist or album URL.

Input parameters:

- `url` (string, required): SoundCloud playlist URL

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/levz0r-beatseek/api-mcp#diagnostics

## Score history

- 2026-11-21: 66
- 2026-11-20: 66
- 2026-11-19: 65
- 2026-11-18: 65
- 2026-11-17: 35
- 2026-11-16: 35
- 2026-11-15: 35
- 2026-11-14: 35
- 2026-11-13: 35
- 2026-11-12: 35
- 2026-11-11: 35
- 2026-11-10: 35
- 2026-11-09: 35
- 2026-11-08: 35
- 2026-11-07: 35

## Common questions

### What is the BeatSeek MCP server?

BeatSeek is an MCP server listed in the public MCP registry as io.github.levz0r/beatseek. SoundCloud search for DJs and AI agents, with BPM and key measured from the audio. This page covers its hosted endpoint (https://beatseek.io/api/mcp).

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

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

BeatSeek exposes 4 tools: search_soundcloud, resolve_track, analyze_track, get_playlist. Their descriptions and schemas cost roughly 415 tokens of context every time the server is loaded.

### Does the BeatSeek MCP server require authentication?

No. We connected to BeatSeek without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the BeatSeek MCP server still maintained?

BeatSeek is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the BeatSeek MCP server?

VerifyMCP ran 12 checks on BeatSeek, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about BeatSeek: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://beatseek.io/api/mcp
- Website: https://beatseek.io/
- Changelog RSS feed: https://verifymcp.io/servers/levz0r-beatseek/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/levz0r-beatseek/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/levz0r-beatseek/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/levz0r-beatseek/api-mcp
