Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BeatSeek

REMOTE · BEATSEEK.IO

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

Available components

+31 this week 66 Trust /100

Last scanned (17 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 480 tokens (~120/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 64% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • 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 hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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 Nov 26 +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.

  • 19 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 18 Nov 26 +30
    • HTTPS: pass → unverified ▼ security
    • HSTS header: pass → fail ▼ security
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Tool coverage: unverified → 100 ▲ functional
    • 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 functional
  • 7 Nov 26 35

    First indexed and scored.

Diagnostics

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 Nov 2026 · Probed https://beatseek.io/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=beatseek.io CN=WE1,O=Google Trust Services,C=US 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA256 f03d07dbc0cf0170e156144bd9d8892
SANs: beatseek.io, *.beatseek.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of beatseek.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
beatseek.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://beatseek.io/api/mcp Verified 200
http (plaintext) http://beatseek.io/api/mcp Inconclusive 405
MCP tools · 4 exposed · ~415 tokens

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 →

Tool Tokens
analyze_track ~125

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.

NameTypeReqDescription
positioninteger–Start of the analysis window in ms; use it for long mixes
urlstringyesSoundCloud track URL

No output schema declared.

No examples provided.

get_playlist ~31

List the tracks of a SoundCloud playlist or album URL.

NameTypeReqDescription
urlstringyesSoundCloud playlist URL

No output schema declared.

No examples provided.

resolve_track ~92

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.

NameTypeReqDescription
artiststring–Primary artist; strongly improves accuracy
limitinteger–Candidates to score
titlestringyes–

No output schema declared.

No examples provided.

search_soundcloud ~167

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.

NameTypeReqDescription
fromDatestring–ISO date, e.g. 2026-01-01
limitinteger––
maxBpmnumber––
minBpmnumber––
querystringyesSearch text
sortstring–'both' blends recency and popularity
toDatestring–ISO date
typestring––

No output schema declared.

No examples provided.

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.

remote · beatseek.io

# add to Claude Code
claude mcp add --transport http levz0r-beatseek 'https://beatseek.io/api/mcp'
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.