Local MCP capabilities provider for Expo
Nothing to run from here
SpotCheck is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
SpotCheck scores a Spotify playlist from 0 to 100 for bot-farm patterns, using public Spotify data, and shows the reasons behind the score. After an artificial streaming warning from a distributor it can scan the playlists involved and draft the reply. Built for independent artists and the people who work with them.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http chris-schofield-spotcheck-mcp https://spotcheck.cc/api/mcp
# 2 — ask your agent for something these tools do
# check_playlist, get_curator_contacts, list_monitors and 4 more
SpotCheck costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codenot declared — it may still work
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, read from the address; if the publisher says otherwise, swap that one word.
claude mcp add --scope user --transport http chris-schofield-spotcheck-mcp https://spotcheck.cc/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| playlist | string | yes | 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:1PmwMQY86 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| playlist | string | yes | Spotify playlist URL, URI, or 22-character playlist ID. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Optional custom display label for the monitor. |
| playlist | string | yes | Spotify playlist URL, URI, or 22-character playlist ID to monitor. |
| track_id | string | no | Optional 22-character Spotify track ID to track placement status alerts for. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| playlist | string | yes | 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 that |
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
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| artistName | string | no | Artist name to fill into the drafted distributor reply and removal requests. |
| distributor | string | no | Distributor name, to address the drafted reply to. |
| links | string | yes | 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 | no | The flagged track name, to fill into drafts. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install SpotCheck or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
11 Nov 2026
latest- The version this listing went live with, after review.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish SpotCheck can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.