_ registry / mcp streamable-http · checked 21m ago

spotcheck

https://spotcheck.cc

Registry code: e4185065bb72568c

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://spotcheck.cc/api/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is spotcheck live?
Yes — it answered the hub's last check (checked 21m ago). It answered 100% of checks over the last 30 days.
Is spotcheck free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does spotcheck have?
7 tools: remove_monitor, check_playlist, add_monitor, get_account_status, list_monitors, scan_warning_playlists, get_curator_contacts.
Is spotcheck safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
523ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 4 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
1 open3 auth-required 3 never probed 4 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_account_status open 3h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_monitors auth-required 3h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • scan_warning_playlists auth-required 3h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "links"
      ],
      "properties": {
        "links": {
          "type": "string",
          "description": "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": {
          "type": "string",
          "description": "The flagged track name, to fill into drafts."
        },
        "artistName": {
          "type": "string",
          "description": "Artist name to fill into the drafted distributor reply and removal requests."
        },
        "distributor": {
          "type": "string",
          "description": "Distributor name, to address the drafted reply to."
        }
      }
    }
    arguments 24 lines
  • get_curator_contacts auth-required 21m ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "playlist"
      ],
      "properties": {
        "playlist": {
          "type": "string",
          "description": "Spotify playlist URL, URI, or 22-character playlist ID."
        }
      }
    }
    arguments 12 lines
  • remove_monitor unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "playlist"
      ],
      "properties": {
        "playlist": {
          "type": "string",
          "description": "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 list_monitors returns as playlist_id (\"1PmwMQY86pJuAm7veFt3u2\")."
        }
      }
    }
    arguments 12 lines
  • check_playlist unknown 21m ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "playlist"
      ],
      "properties": {
        "playlist": {
          "type": "string",
          "description": "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:1PmwMQY86pJuAm7veFt3u2\") or the bare 22-character base-62 id (\"1PmwMQY86pJuAm7veFt3u2\"). Album, track and artist links are rejected with INVALID_PARAMS."
        }
      }
    }
    arguments 12 lines
  • add_monitor unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "playlist"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Optional custom display label for the monitor."
        },
        "playlist": {
          "type": "string",
          "description": "Spotify playlist URL, URI, or 22-character playlist ID to monitor."
        },
        "track_id": {
          "type": "string",
          "description": "Optional 22-character Spotify track ID to track placement status alerts for."
        }
      }
    }
    arguments 20 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e4185065bb72568c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e4185065bb72568c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e4185065bb72568c/badge.svg)](https://brick.blue/agent/e4185065bb72568c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.