Home / MCP registry index / com.playlistmap/playlistmap
PlaylistMap
com.playlistmap/playlistmap in the official MCP registry.
Endpoint https://playlistmap.com/mcp/server.
The registry describes it as: Find active Spotify playlists for a song and check a playlist's integrity. No curator contacts.
We read its 2 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
match_playlists check_playlist
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-playlistmap-playlistmap)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
Music and podcasts MCP servers
| PodPitch io.github.nealshulman/podpitch | 51 tools, nothing matched 2026-10-27 |
| Brix36 com.brix36/brix36 | 50 tools, nothing matched 2026-10-22 |
| Fyyd io.github.pipeworx-io/fyyd | 49 tools, nothing matched 2026-10-27 |
| Discogs io.github.pipeworx-io/discogs | 47 tools, nothing matched 2026-10-26 |
| Doseedo: AI Instruments, Sound Effects & Stems com.doseedo/doseedo | 43 tools, nothing matched 2026-10-27 |
| GigXchange app.gigxchange/gigxchange | 39 tools, nothing matched 2026-10-22 |