Great DJ MCP server
io.github.ruiramos/greatdjruiramosstreamable-httpv1.0.0Scanned
Search songs and make, edit and share music playlists on great.dj. Works without an account.
11 tools: 3 can delete or cancel things, 1 do something that can't be undone, 3 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Great DJ MCP server can do
The Great DJ MCP server is published by the GitHub account ruiramos. It has 11 tools. It can delete or cancel things (3 tools: update_playlist, restore_playlist_version and delete_playlist), do things that cannot be undone, such as sending, paying or publishing (create_playlist) and create or change data (3 tools: playlist_history, add_songs and import_spotify_playlist). 4 tools only read.
2 tools bring in text other people can write (search_songs and import_spotify_playlist); 1 tool can send data out of your system (import_spotify_playlist).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Deletes or cancels 3Claude Code: deny
delete_playlistDeletes one of the API key account's playlists, with its history.No findings
Why it is in this group
- The name "delete_playlist" says "delete": a word for removing or ending something.
- The description says "Can't be undone".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Deletes one of the API key account's playlists, with its history. Can't be undone: confirm with the user first. Needs an API key.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
restore_playlist_versionMakes an earlier version (an id from playlist_history) the current playlist, saved as a new version (nothing is lost).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Makes an earlier version (an id from playlist_history) the current playlist, saved as a new version (nothing is lost). Owner only: the API key's account, or the edit_token of an anonymous playlist.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
update_playlistChanges a playlist's title, description or privacy, and/or replaces its whole song list with `songs` (to reorder or remove songs: send the full new list, using the video ids from g…No findings
Why it is in this group
- The name "update_playlist" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Changes a playlist's title, description or privacy, and/or replaces its whole song list with `songs` (to reorder or remove songs: send the full new list, using the video ids from get_playlist). Each change is saved as a new version (see playlist_history). Each song is a {"id": "<YouTube video id>"} object (preferred: free and exact) or an "Artist - Title" string, looked up on YouTube (slow, and limited per hour). Reuse the video ids returned by search_songs and earlier calls instead of looking songs up again. Title, description and privacy: owner only (API key, or edit_token for anonymous playlists). Songs: also anyone, for open playlists.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
Can't be undone 1Claude Code: ask
create_playlistMakes a new great.dj playlist and returns its link, its tracks with their YouTube video ids (reuse those ids in later calls), and any songs that weren't found.No findings
Why it is in this group
- The name "create_playlist" says "create": a word for a change.
- The description says "can't be recovered".
Description, as the server wrote it Makes a new great.dj playlist and returns its link, its tracks with their YouTube video ids (reuse those ids in later calls), and any songs that weren't found. Each song is a {"id": "<YouTube video id>"} object (preferred: free and exact) or an "Artist - Title" string, looked up on YouTube (slow, and limited per hour). Reuse the video ids returned by search_songs and earlier calls instead of looking songs up again. With an API key it belongs to the key's account. Without one it's an anonymous public playlist and the result has an edit_token: keep it for the rest of the conversation, it's the only way to change the playlist later and can't be recovered.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: false
Changes things 3Claude Code: ask
add_songsAppends songs to the end of a playlist.No findings
Why it is in this group
- The name "add_songs" says "add": a word for a change.
Description, as the server wrote it Appends songs to the end of a playlist. Each song is a {"id": "<YouTube video id>"} object (preferred: free and exact) or an "Artist - Title" string, looked up on YouTube (slow, and limited per hour). Reuse the video ids returned by search_songs and earlier calls instead of looking songs up again. For your own playlists (API key), anonymous ones you made (edit_token), and open ones anyone can edit.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: false
import_spotify_playlistMakes a great.dj playlist (owned by the API key's account) from a public Spotify playlist's first 50 songs, each looked up on YouTube (uses up song lookups).Reads text others writeCan send data outNo findings
Why it is in this group
- The name "import_spotify_playlist" says "import": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Makes a great.dj playlist (owned by the API key's account) from a public Spotify playlist's first 50 songs, each looked up on YouTube (uses up song lookups). Needs an API key.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: false
- openWorldHint: true
playlist_historyThe saved versions of a playlist, newest first (for restore_playlist_version).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The saved versions of a playlist, newest first (for restore_playlist_version). Owner only: the API key's account, or the edit_token of an anonymous playlist.
Annotations the server declares
- readOnlyHint: true
Only reads 4Show 4 read-only tools
get_playlistA great.dj playlist: title, description, owner, link and its tracks (with their YouTube video ids).No findings
Why it is in this group
- The name "get_playlist" says "get": a word for reading.
Description, as the server wrote it A great.dj playlist: title, description, owner, link and its tracks (with their YouTube video ids). Any playlist can be read by anyone with its id or link.
Annotations the server declares
- readOnlyHint: true
get_popular_playlistsgreat.dj's popular playlists right now (title, owner, link, track count; no tracks: use get_playlist for those).No findings
Why it is in this group
- The name "get_popular_playlists" says "get": a word for reading.
Description, as the server wrote it great.dj's popular playlists right now (title, owner, link, track count; no tracks: use get_playlist for those).
Annotations the server declares
- readOnlyHint: true
list_my_playlistsThe playlists of the API key's account, newest first, 20 per page (no tracks: use get_playlist for those).No findings
Why it is in this group
- The name "list_my_playlists" says "list": a word for reading.
Description, as the server wrote it The playlists of the API key's account, newest first, 20 per page (no tracks: use get_playlist for those). Needs an API key.
Annotations the server declares
- readOnlyHint: true
search_songsFinds a song on YouTube: up to 3 matching videos (id, title, thumbnail).Reads text others writeNo findings
Why it is in this group
- The name "search_songs" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Finds a song on YouTube: up to 3 matching videos (id, title, thumbnail). Use the returned video ids in create_playlist, add_songs and update_playlist instead of the song's name, so it isn't looked up again. Each search not seen before uses up song lookups (limited per hour), so search only for songs you need.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:20 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (3 destructive, 1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.great.dj/mcp: tools/list returned 11 tools to an anonymous client, including update_playlist (destructive), restore_playlist_version (destructive), delete_playlist (destructive), create_playlist (irreversible), playlist_history (write) and 2 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http greatdj https://api.great.dj/mcpclaude mcp add --transport http greatdj https://api.great.dj/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__greatdj__search_songs",
"mcp__greatdj__get_playlist",
"mcp__greatdj__get_popular_playlists",
"mcp__greatdj__list_my_playlists"
],
"ask": [
"mcp__greatdj__playlist_history",
"mcp__greatdj__create_playlist",
"mcp__greatdj__add_songs",
"mcp__greatdj__import_spotify_playlist"
],
"deny": [
"mcp__greatdj__update_playlist",
"mcp__greatdj__restore_playlist_version",
"mcp__greatdj__delete_playlist"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as greatdj. Review it before you use it.
Capability tags behind 2 rules
- mcp__greatdj__search_songs untrusted-input
- mcp__greatdj__import_spotify_playlist untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ruiramos/greatdj/verify?hash=ea2bb47ef2ebb5a04efd048a663912e6d426aeb51700c670a29506917a5ea292" | jq -e '.changed == false'Pinned hash ea2bb47ef2eb, from Nov 20, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.ruiramos/greatdj/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.ruiramos/greatdj)Source: MCP Registry. Synced Nov 20, 2026, 10:18 UTC.
Great DJ MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Great DJ MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Great DJ MCP server delete data?
- Yes. 3 tools can delete, cancel or revoke something: update_playlist, restore_playlist_version and delete_playlist.
Can the Great DJ MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: create_playlist.
What tools does the Great DJ MCP server have?
- 11 tools: 3 destructive, 1 irreversible, 3 write, 4 read. update_playlist, restore_playlist_version, delete_playlist, create_playlist, playlist_history, add_songs, import_spotify_playlist, search_songs and 3 more.
Does the Great DJ MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Great DJ MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): import_spotify_playlist.
Has the Great DJ MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.