Skip to content

SpotCheck MCP server

io.github.chrisschouk/spotcheckchrisschoukstreamable-httpv1.0.1Scanned

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

7 tools: 1 can delete or cancel things, 3 change things and 3 only read.

Tools: 1 delete, 0 irreversible, 3 write, 3 read.
  • Reads private data · 1
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

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

The SpotCheck MCP server is published by the GitHub account chrisschouk. It has 7 tools. It can delete or cancel things (1 tool: remove_monitor) and create or change data (3 tools: check_playlist, add_monitor and scan_warning_playlists). 3 tools only read.

1 tool reads private data (get_curator_contacts); 3 tools bring in text other people can write (check_playlist, get_curator_contacts and scan_warning_playlists).

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, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.0.1.

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.

7 tools

Deletes or cancels 1Claude Code: deny
  • remove_monitorStops cloud monitoring for one playlist on the signed-in Premium account.No findings

    Why it is in this group

    • The name "remove_monitor" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Remove Playlist from Cloud Monitoring
    • readOnly: false
    • isConsequential: true
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • tags: spotify,monitoring,mutation
Changes things 3Claude Code: ask
  • add_monitorEnrolls a Spotify playlist in automated cloud monitoring for daily follower snapshots, growth trend analysis, and inorganic spike alerts.No findings

    Why it is in this group

    • The name "add_monitor" says "add": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Add Playlist to Cloud Monitoring
    • readOnly: false
    • isConsequential: true
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • tags: spotify,monitoring,cloud-tracking,mutation
  • check_playlistScores one Spotify playlist for bot and fake-follower risk.Reads text others writeNo 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.

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

    Annotations the server declares

    • title: Check Spotify Playlist Bot Risk
    • readOnly: true
    • isConsequential: false
    • readOnlyHint: true
    • openWorldHint: true
    • tags: spotify,playlist,bot-detection,validation
  • scan_warning_playlistsScores every Spotify playlist an artist pastes after a distributor flags a track for artificial streaming (the full list from Spotify for Artists).Reads text others writeNo 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.

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

    Annotations the server declares

    • title: Scan Playlists After a Distributor Warning
    • readOnly: true
    • isConsequential: false
    • readOnlyHint: true
    • openWorldHint: true
    • tags: spotify,playlist,bot-detection,warning-scan,curator-outreach
Only reads 3Show 3 read-only tools
  • get_account_statusDescribes who SpotCheck thinks the caller is and what they can do right now.No findings

    Why it is in this group

    • The name "get_account_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get SpotCheck Account Entitlement and Status
    • readOnly: true
    • isConsequential: false
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
    • tags: account,status,entitlements
  • get_curator_contactsExtracts public submission contact channels (emails, Instagram, X/Twitter, TikTok handles, and submission links) from a Spotify playlist description, along with researched curator …Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_curator_contacts" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_curator_contacts" says "get" and "contact": it reads contacts.
    • private-dataThe description's first sentence says "contact": it reads contacts.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get Playlist Curator Submission Contacts
    • readOnly: true
    • isConsequential: false
    • readOnlyHint: true
    • openWorldHint: true
    • tags: spotify,curator,contacts,promotion,email
  • list_monitorsLists 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 tim…No findings

    Why it is in this group

    • The name "list_monitors" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List Cloud-Monitored Playlists
    • readOnly: true
    • isConsequential: false
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
    • tags: spotify,monitoring,cloud-tracking

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

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
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 16, 2026, 14:21 UTC, unchanged since Nov 16, 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
4
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://spotcheck.cc/.well-known/oauth-protected-resource
Authorization servers
https://spotcheck.cc
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://spotcheck.cc/api/mcp: tools/list returned 7 tools to an anonymous client, including remove_monitor (destructive), check_playlist (write), add_monitor (write), scan_warning_playlists (write)

    What this check looks for

Posture changes

  1. Nov 16, 2026
    • Tools that change things, listed without credentials: 3 to 4

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.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 4.View diff
    • Tools that change things, listed without credentials: 3 to 4
  2. Tools7 changed.~7 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http spotcheck https://spotcheck.cc/api/mcp
claude mcp add --transport http spotcheck https://spotcheck.cc/api/mcp

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__spotcheck__get_curator_contacts",
      "mcp__spotcheck__list_monitors",
      "mcp__spotcheck__get_account_status"
    ],
    "ask": [
      "mcp__spotcheck__check_playlist",
      "mcp__spotcheck__add_monitor",
      "mcp__spotcheck__scan_warning_playlists"
    ],
    "deny": [
      "mcp__spotcheck__remove_monitor"
    ]
  }
}

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

Capability tags behind 3 rules
  • mcp__spotcheck__check_playlist untrusted-input
  • mcp__spotcheck__get_curator_contacts private-data, untrusted-input
  • mcp__spotcheck__scan_warning_playlists untrusted-input

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.chrisschouk/spotcheck/verify?hash=706f840d89815619049b6da91ae53f080724608422ab922cd54a2866f320b79c" | jq -e '.changed == false'

Pinned hash 706f840d8981, from Nov 9, 2026, 12: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.chrisschouk/spotcheck/changes.xml

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

Badge

Anlyon Radar badge for io.github.chrisschouk/spotcheck
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.chrisschouk/spotcheck.svg)](https://radar.anlyon.com/servers/io.github.chrisschouk/spotcheck)

Source: MCP Registry · repository. Synced Nov 9, 2026, 12:18 UTC.

SpotCheck MCP server: questions and answers

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

Is the SpotCheck MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 4 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 SpotCheck MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: remove_monitor.

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

7 tools: 1 destructive, 3 write, 3 read. remove_monitor, check_playlist, add_monitor, scan_warning_playlists, get_curator_contacts, list_monitors and get_account_status.

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

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

Does the SpotCheck MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the SpotCheck MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.