# SpotCheck (remote · spotcheck.cc)

Score Spotify playlists for bot-farm patterns and triage an artificial streaming warning.

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

> **Recent critical change**: Authorization (2026-11-13). See the changelog below before you install this server.

## Components

- remote · `spotcheck.cc`: 68/100 (this document), [markdown](https://verifymcp.io/servers/chrisschouk-spotcheck/api-mcp.md), [page](https://verifymcp.io/servers/chrisschouk-spotcheck/api-mcp)

## Channel facts

- Endpoint: `https://spotcheck.cc/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (remove_monitor).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1472 tokens (~210/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

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

SpotCheck is a hosted endpoint at https://spotcheck.cc/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.

### Claude

```bash
claude mcp add --transport http chrisschouk-spotcheck 'https://spotcheck.cc/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "chrisschouk-spotcheck": {
      "url": "https://spotcheck.cc/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "chrisschouk-spotcheck": {
      "type": "http",
      "url": "https://spotcheck.cc/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.chrisschouk-spotcheck]
url = "https://spotcheck.cc/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chrisschouk-spotcheck": {
      "type": "remote",
      "url": "https://spotcheck.cc/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add chrisschouk-spotcheck --url 'https://spotcheck.cc/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  chrisschouk-spotcheck:
    url: "https://spotcheck.cc/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "chrisschouk-spotcheck": {
      "Transport": "http",
      "Url": "https://spotcheck.cc/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add chrisschouk-spotcheck -t streamable-http -u 'https://spotcheck.cc/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "chrisschouk-spotcheck": {
      "type": "http",
      "url": "https://spotcheck.cc/api/mcp"
    }
  }
}
```

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-19 (score 68, +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-17 (score 67, +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-11-15 (score 66, +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-11-13 (score 65, +1)

- [critical regression] Authorization: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.17

### 2026-11-12 (score 64, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.10 → unverified
- [security regression] Authorization: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-11 (score 64, +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-11-09 (score 63, +1)

- [critical regression] Authorization: unverified → fail
- [security] Tool “add_monitor” rewrote its description, which is the text the model reads
- [security] Tool “check_playlist” rewrote its description, which is the text the model reads
- [security] Tool “get_account_status” rewrote its description, which is the text the model reads
- [security] Tool “list_monitors” rewrote its description, which is the text the model reads
- [security] Tool “remove_monitor” rewrote its description, which is the text the model reads
- [security] Tool “scan_warning_playlists” rewrote its description, which is the text the model reads
- [security] Tool “remove_monitor” is now declared destructive
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [functional] Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
- [cosmetic] “check_playlist” reworded the description of “playlist”
- [cosmetic] “remove_monitor” reworded the description of “playlist”

### 2026-11-08 (score 62)

First indexed and scored.

## MCP tools (7)

### `check_playlist` (~437 tokens)

Scores one Spotify playlist for bot and fake-follower risk. Returns the playlist (id, name, curator, followers, tracks, url), botRisk.score from 0 to 100, botRisk.level (low, medium, high or editorial), the warning factors behind the score (follower-to-track ratio, generic naming, sudden follower spikes and similar), the caller tier, and the follower snapshots SpotCheck holds for the last 31 days. Use it when the question is about a single playlist, such as one an artist is about to pitch to or has just been added to. For a whole list pasted from Spotify for Artists after a distributor artificial-streaming warning, use scan_warning_playlists instead: it ranks up to 50 playlists in one call and drafts the replies. Limits: anonymous callers get 1 check a day and signed-in Free accounts 3; Free responses show only the most severe factor (lockedFactors counts the hidden ones) and no snapshots. Pro (£4.99/mo) and Premium (£14.99/mo) are unlimited and get every factor and the snapshot history. Call get_account_status to see what is left today. Read-only: it reads public Spotify data and stored snapshots and changes nothing apart from the daily usage count, which is refunded if Spotify fails. Errors: INVALID_PARAMS (not a playlist link), NOT_FOUND (deleted or private), SPOTIFY_PLAYLIST (Spotify-owned editorial or algorithmic playlists, which the API does not expose), UNVERIFIABLE, RATE_LIMITED (daily allowance used).

Input parameters:

- `playlist` (string, required): Spotify playlist to look up, in any of three forms: a share URL ("https://open.spotify.com/playlist/1PmwMQY86pJuAm7veFt3u2", query strings such as ?si= are ignored), a URI ("spotify:playlist:1PmwMQY8…

### `get_curator_contacts` (~67 tokens)

Extracts public submission contact channels (emails, Instagram, X/Twitter, TikTok handles, and submission links) from a Spotify playlist description, along with researched curator pitch guidance when available.

Input parameters:

- `playlist` (string, required): Spotify playlist URL, URI, or 22-character playlist ID.

### `list_monitors` (~65 tokens)

Lists all playlists currently tracked under 24/7 cloud monitoring for the authenticated account, including 24-hour and 7-day follower deltas, anomaly flags, and latest snapshot timestamps. For one playlist's full 31-day snapshot series, call check_playlist with its playlist_id.

### `add_monitor` (~124 tokens)

Enrolls a Spotify playlist in automated cloud monitoring for daily follower snapshots, growth trend analysis, and inorganic spike alerts. Allows up to 25 monitored playlists per Premium account. Adding a playlist that is already monitored leaves its existing name and track_id unchanged; to change them, call remove_monitor first.

Input parameters:

- `name` (string): Optional custom display label for the monitor.
- `playlist` (string, required): Spotify playlist URL, URI, or 22-character playlist ID to monitor.
- `track_id` (string): Optional 22-character Spotify track ID to track placement status alerts for.

### `remove_monitor` (~340 tokens)

Stops cloud monitoring for one playlist on the signed-in Premium account. The daily follower snapshot, the spike and drop alert emails and the track-removed alert all stop for that playlist on this account, and it disappears from list_monitors. Returns { ok, message, playlistId }. Side effects: deletes this account's monitor entry, including its custom name and track_id. Follower snapshots already stored for the playlist are kept and still appear in check_playlist, and other accounts monitoring the same playlist are unaffected. Reversible with add_monitor, but the name and track_id have to be supplied again. Idempotent: removing a playlist that is not monitored still returns ok: true. Use it to free a slot when the account is at the 25-monitor limit, or to change a monitor's name or tracked track (there is no update tool, so remove it and call add_monitor with the new values). Call list_monitors first if you need the exact playlist id. Requires Premium (£14.99/mo) and a signed-in account: returns FORBIDDEN on other tiers, UNAUTHORIZED without an account, and INVALID_PARAMS for a link that is not a playlist.

Input parameters:

- `playlist` (string, required): The monitored playlist to stop tracking, as a share URL ("https://open.spotify.com/playlist/1PmwMQY86pJuAm7veFt3u2"), a URI ("spotify:playlist:1PmwMQY86pJuAm7veFt3u2") or the bare 22-character id tha…

### `get_account_status` (~209 tokens)

Describes who SpotCheck thinks the caller is and what they can do right now. Returns email (null when anonymous), tier (free, pro or premium), isAnonymous, authMethod (oauth, session, api_key, anonymous or env_override), features (playlistChecking, fullFactorBreakdown, historicalTrends, curatorContacts, cloudMonitoring, maxMonitors), allowance (dailyChecksRemaining and unlimited; usageUnavailable is set when today's count could not be read) and upgradeUrl (null on paid tiers). Use it before other calls to plan: whether check_playlist has checks left today (anonymous 1 a day, Free 3, Pro and Premium unlimited), whether get_curator_contacts and the monitor tools will work (Premium, £14.99/mo), and whether the full factor breakdown is unlocked (Pro, £4.99/mo, or Premium). Takes no arguments, works without signing in, costs nothing and does not use up a check. Read-only and safe to repeat.

### `scan_warning_playlists` (~230 tokens)

Scores every Spotify playlist an artist pastes after a distributor flags a track for artificial streaming (the full list from Spotify for Artists). Use it for a batch of up to 50 links; for one playlist, use check_playlist, which also works anonymously. Returns each playlist ranked by bot-risk score with skip reasons for invalid or unavailable links. Free accounts get up to 2 scans a day with only the worst flagged playlist unlocked; Pro and Premium are unlimited with the full ranked report. Requires a signed-in account (anonymous callers are not supported). Supply artistName, trackName and distributor to also receive drafted reply text once the report is unlocked.

Input parameters:

- `artistName` (string): Artist name to fill into the drafted distributor reply and removal requests.
- `distributor` (string): Distributor name, to address the drafted reply to.
- `links` (string, required): Spotify playlist links, URIs or ids, one per line (also accepts comma or space separated), as pasted from Spotify for Artists. Up to 50.
- `trackName` (string): The flagged track name, to fill into drafts.

## Diagnostics

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

## Score history

- 2026-11-21: 68
- 2026-11-20: 68
- 2026-11-19: 68
- 2026-11-18: 67
- 2026-11-17: 67
- 2026-11-16: 66
- 2026-11-15: 66
- 2026-11-14: 65
- 2026-11-13: 65
- 2026-11-12: 64
- 2026-11-11: 64
- 2026-11-10: 63
- 2026-11-09: 63
- 2026-11-08: 62

## Common questions

### What is the SpotCheck MCP server?

SpotCheck is an MCP server listed in the public MCP registry as io.github.chrisschouk/spotcheck. Score Spotify playlists for bot-farm patterns and triage an artificial streaming warning. This page covers its hosted endpoint (https://spotcheck.cc/api/mcp).

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

SpotCheck scores 68 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 SpotCheck MCP server expose?

SpotCheck exposes 7 tools: check_playlist, get_curator_contacts, list_monitors, add_monitor, remove_monitor, and 2 more. Their descriptions and schemas cost roughly 1,472 tokens of context every time the server is loaded.

### Does the SpotCheck MCP server require authentication?

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

### Is the SpotCheck MCP server still maintained?

SpotCheck 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 SpotCheck MCP server?

VerifyMCP ran 13 checks on SpotCheck, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.

## Links

- Remote endpoint: https://spotcheck.cc/api/mcp
- Repository: https://github.com/chrisschouk/spotcheck
- Website: https://spotcheck.cc/
- Changelog RSS feed: https://verifymcp.io/servers/chrisschouk-spotcheck/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/chrisschouk-spotcheck/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/chrisschouk-spotcheck/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/chrisschouk-spotcheck/api-mcp
