Skip to content

PlaylistMap MCP server

com.playlistmap/playlistmapplaylistmap.comstreamable-httpv1.1.0Scanned

Find active Spotify playlists for a song and check a playlist's integrity. No curator contacts.

2 tools: 2 only read.

Tools: 0 delete, 0 irreversible, 0 write, 2 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

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 PlaylistMap MCP server can do

The PlaylistMap MCP server is published by playlistmap.com, a domain the MCP Registry verified. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

2 tools bring in text other people can write (match_playlists and check_playlist); 1 tool can send data out of your system (check_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 9, 2026, version 1.1.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.

2 tools

Only reads 2Show 2 read-only tools
  • check_playlistReturns a 0-100 integrity estimate for a public Spotify playlist with confidence and contributing factors (follower and engagement patterns, curator activity), plus whether Playlis…Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Returns a 0-100 integrity estimate for a public Spotify playlist with confidence and contributing factors (follower and engagement patterns, curator activity), plus whether PlaylistMap tracks it. Input: a playlist URL or its 22-character id. Screening signal from public data, not proof.

    Annotations the server declares

    • title: Check a Spotify playlist's integrity
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • match_playlistsReturns currently active Spotify playlists that fit a song or description, with follower counts, fit reasons and a results_url for the full list.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Returns currently active Spotify playlists that fit a song or description, with follower counts, fit reasons and a results_url for the full list. Input: a Spotify track link or a free-text description of the song, optionally the artist and a genre. Curator names and contacts are not returned.

    Annotations the server declares

    • title: Find Spotify playlists for a song
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: 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.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:22 UTC, unchanged since Oct 24, 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
0
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

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.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http playlistmap https://playlistmap.com/mcp/server
claude mcp add --transport http playlistmap https://playlistmap.com/mcp/server

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__playlistmap__match_playlists"
    ],
    "ask": [
      "mcp__playlistmap__check_playlist"
    ],
    "deny": []
  }
}

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 playlistmap. Review it before you use it.

Capability tags behind 2 rules
  • mcp__playlistmap__match_playlists untrusted-input
  • mcp__playlistmap__check_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/com.playlistmap/playlistmap/verify?hash=b2cf2735517fc1e3fdbd060bb7c7f8e78d29a42e545cf21d90e7e898f8a1fca6" | jq -e '.changed == false'

Pinned hash b2cf2735517f, from Nov 9, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.playlistmap/playlistmap/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.playlistmap/playlistmap
[![Anlyon Radar](https://radar.anlyon.com/badge/com.playlistmap/playlistmap.svg)](https://radar.anlyon.com/servers/com.playlistmap/playlistmap)

Source: MCP Registry. Synced Oct 24, 2026, 10:17 UTC.

PlaylistMap MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the PlaylistMap MCP server safe?

No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the PlaylistMap MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the PlaylistMap MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the PlaylistMap MCP server have?

2 tools: 2 read. match_playlists and check_playlist.

Does the PlaylistMap MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the PlaylistMap 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): check_playlist.

Has the PlaylistMap MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.