# PlaylistMap (remote · playlistmap.com)

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

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

## Components

- remote · `playlistmap.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-playlistmap-playlistmap/mcp-server.md), [page](https://verifymcp.io/servers/com-playlistmap-playlistmap/mcp-server)

## Channel facts

- Endpoint: `https://playlistmap.com/mcp/server`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 369 tokens (~184/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (50% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the PlaylistMap MCP server?

PlaylistMap is a hosted endpoint at https://playlistmap.com/mcp/server, 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 com-playlistmap-playlistmap 'https://playlistmap.com/mcp/server'
```

### Cursor

```json
{
  "mcpServers": {
    "com-playlistmap-playlistmap": {
      "url": "https://playlistmap.com/mcp/server"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-playlistmap-playlistmap": {
      "type": "http",
      "url": "https://playlistmap.com/mcp/server"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-playlistmap-playlistmap]
url = "https://playlistmap.com/mcp/server"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-playlistmap-playlistmap": {
      "type": "remote",
      "url": "https://playlistmap.com/mcp/server",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-playlistmap-playlistmap --url 'https://playlistmap.com/mcp/server' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-playlistmap-playlistmap:
    url: "https://playlistmap.com/mcp/server"
```

### Netclaw

```json
{
  "McpServers": {
    "com-playlistmap-playlistmap": {
      "Transport": "http",
      "Url": "https://playlistmap.com/mcp/server"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-playlistmap-playlistmap -t streamable-http -u 'https://playlistmap.com/mcp/server'
```

### Other

```json
{
  "mcpServers": {
    "com-playlistmap-playlistmap": {
      "type": "http",
      "url": "https://playlistmap.com/mcp/server"
    }
  }
}
```

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-04 (score 75, +1)

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

### 2026-11-02 (score 74, +1)

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

### 2026-10-31 (score 73, +1)

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

### 2026-10-29 (score 72, +1)

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

### 2026-10-27 (score 71, +1)

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

### 2026-10-25 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 70)

First indexed and scored.

## MCP tools (2)

### `match_playlists` (~123 tokens)

Find Spotify playlists for a song

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.

Input parameters:

- `artist` (string): Artist name (optional, improves matching).
- `genre` (string): Primary genre (optional, e.g. "tech house", "bedroom pop").
- `song` (string, required): Spotify track URL, or a free-text description of the song.

Output parameters:

- `artist` (string)
- `documentation_url` (string)
- `matches` (array)
- `note` (string)
- `results_url` (string)
- `showing` (integer)
- `song` (string)
- `total_matches` (integer)

### `check_playlist` (~80 tokens)

Check a Spotify playlist's integrity

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.

Input parameters:

- `url` (string, required): Spotify playlist URL or 22-character playlist id.

## Diagnostics

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

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 72
- 2026-10-29: 72
- 2026-10-28: 71
- 2026-10-27: 71
- 2026-10-26: 70
- 2026-10-25: 70
- 2026-10-24: 70

## Common questions

### What is the PlaylistMap MCP server?

PlaylistMap is an MCP server listed in the public MCP registry as com.playlistmap/playlistmap. Find active Spotify playlists for a song and check a playlist's integrity. No curator contacts. This page covers its hosted endpoint (https://playlistmap.com/mcp/server).

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

PlaylistMap scores 75 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 PlaylistMap MCP server expose?

PlaylistMap exposes 2 tools: match_playlists, check_playlist. Their descriptions and schemas cost roughly 203 tokens of context every time the server is loaded.

### Does the PlaylistMap MCP server require authentication?

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

### Is the PlaylistMap MCP server still maintained?

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

## Links

- Remote endpoint: https://playlistmap.com/mcp/server
- Website: https://playlistmap.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-playlistmap-playlistmap/mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-playlistmap-playlistmap/mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/com-playlistmap-playlistmap/mcp-server