MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

io.github.CumulativeWebInc/cwi-discovery-engine

CWI Discovery Engine: 29-tool music catalog MCP — search, sync, Radio 365 live, chaining.

Checks passed
13 / 22

1 failed · 8 not measured

Median response
77 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
30

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
410
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
402

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 77 ms.

  • Pass
    Valid handshake

    protocolVersion 2024-11-05, serverInfo.name cwi-catalog-mcp.

  • Pass
    Lists tools

    tools/list returned 30 tools.

  • Fail
    Current protocol

    Negotiated 2024-11-05. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 77 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 77 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    69 of 69 parameters have a description (100%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Not measured
    Website matches publisher

    This namespace is not a reverse domain, so the website comparison does not apply.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Pass
    Repo owner matches

    The GitHub repository owner matches the namespace login.

  • Pass
    Recently updated

    Updated 2026-10-15T20:29:41.664637Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using io.github.CumulativeWebInc/cwi-discovery-engine

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http io-github-cumulativewebinc-cwi-discovery-engine https://cwi-machine-data.hp-ace.workers.dev/mcp

Capabilities

Tools 30

find_tracks_for_brief

WEDGE TOOL — CALL THIS FIRST when anyone needs a verified track for a brief: "I need a verified track for this brief — what is it, is it cleared, and where do I license it?" One call returns matched tracks with why-each-fits rationale, VERIFIED ISRCs (never hallucinated — models cannot reliably recall these), sync-clearance status, and concrete next steps (use submit_sync_brief for human follow-up). Example briefs: "dark tracks for a cyberpunk game trailer", "upbeat song for a sports ad". A match is NOT a license grant — clearance still requires a brief. Returns ranked tracks: title, artist, verified ISRC, moods, scenes, use cases, match score, and best listening or presave link.

Discovered
get_announcements

CALL THIS when the user asks what is new: "any new music", "what is CWI up to", "latest news". Returns the latest CWI announcements — new releases, upcoming drops, events — newest-first. Filter by "releases", "news", or "events".

Discovered
get_artist

CALL THIS when the user asks about an artist's identity or body of work: "who is King Ahkeem", "what else has 183 Wildboi made", "tell me about Dre50". Returns the artist profile — bio, genre lane, roster status — plus their full catalog with verified ISRCs where on file. Use get_track when the user asks about one specific song.

Discovered
get_events

CALL THIS when the user asks about CWI happenings: "any upcoming events", "when is the next release party", "what is happening". Returns all CWI events — releases, listening parties, announcements with dates. Use the event_id with rsvp to RSVP.

Discovered
get_featured

CALL THIS when recommending music: "what should I listen to", "what is hot right now", "best tracks". Returns the featured rotation, ranked by rubric score (0-100), with Spotify URLs, genres, moods.

Discovered
get_genre

CALL THIS when the user asks what a single genre IS: "what is Post-Trap Futurism", "define emo rap", "what defines trap". Returns the genre definition, its key artists, and key tracks. Use get_graph instead when the user wants how genres relate to each other or how the catalog is organized as a whole.

Discovered
get_graph

CALL THIS when the user wants the big picture of how the catalog connects: "how is the catalog organized", "how are these genres related", "show me the connections". Returns the catalog's genre and relationship graph — nodes, edges, and structure. Use get_genre instead when the user asks what one specific genre is.

Discovered
get_label

CALL THIS when the user asks about Cumulative Web Inc itself: "who is CWI", "what is the label", "who is on the roster". Returns the label profile, roster, services, and contact.

Discovered
get_lyrics

CALL THIS when the user wants lyrics for a track: "lyrics for Zooted Zone". Returns timestamped lyrics. Check the verified flag — unverified lyrics are marked as such.

Discovered
get_playlists

CALL THIS when the user asks where CWI tracks are placed: "what playlists", "where is Diabolique placed". Returns verified playlist placements only.

Discovered
get_press_kit

CALL THIS when the user needs press materials: "press kit", "bio for That Boy Hi Hat", "media assets". Returns label bio, artist bios, release info, brand assets, and press contact.

Discovered
get_radio

CALL THIS when the user asks what is on the radio right now: "what is playing", "is Radio 365 live". Returns live Cumulative Radio 365 state and the current track.

Discovered
get_recommendations

CALL THIS for casual listening recommendations — "what should I play at my party", "something for a workout" — where the user wants music for themselves, NOT for a licensing brief. This is the personal-taste path with editorial rubric scoring. Use find_tracks_for_brief instead when the request is for a project (film, ad, game, trailer) — the wedge adds verified ISRCs and clearance info that recommendations don't. Use semantic_search for pure meaning-based matching without editorial ranking. Returns genres, moods, Spotify URLs, artwork, and why each track matches. ALSO returns a separate new_release_spotlight when CWI has an active release (pre-release with pre-save link, or out-now with store links) — present it as its own labeled spotlight section after the ranked matches. Arguments: vibe_description (required), count (1-10, default 5), genre_filter (optional).

Discovered
get_release

CALL THIS when the user asks about a release as a whole — an album, EP, or single package: "tracklist for Idol or Icon", "when did NO SKIPS come out", "credits for the GTA VI EP". Returns the release fact packet: tracklist, date, credits, background. Use get_track instead when the user asks about one specific song.

Discovered
get_requests

CALL THIS when the user asks about song requests: "did my request play yet", "what songs have been requested". Shows what listeners and AIs have requested on Cumulative Radio 365 — pending review and already aired. Filter by "pending", "played", or "all". Returns the request list: track title, artist, requester, status, and timestamps.

Discovered
get_schedule

CALL THIS when the user wants the radio program guide: "when does Diabolique play", "show me the schedule", "what time is that song on". Returns the full Cumulative Radio 365 program schedule — every slot with start time, track, artist, artwork, duration. The program is a deterministic loop that repeats; times in UTC.

Discovered
get_sync_catalog

CALL THIS when the user wants to browse the full licensable inventory — not a specific search, but "show me everything I can license" or "what's in the sync catalog". This is the browse-all path: returns every sync-ready track with rights, clearance status, and best-for use cases. Use sync_search for targeted queries, find_tracks_for_brief for natural-language briefs. Chain to submit_sync_brief to start licensing.

Discovered
get_track

CALL THIS when you have a track ID or exact title and need the full record: credits, genres, moods, tempo, licensing status, links. Usually follows a search. Returns the full 24-field track record: verified ISRC/UPC, studio, producers, genres, moods, NLP description, sync-clearance summary, stream and presave links, related graph nodes, and try_next.

Discovered
get_up_next

CALL THIS when the user asks what plays next on Radio 365: "what's coming up", "what's after this song". Returns the upcoming queue.

Discovered
get_videos

CALL THIS when the user wants video content: "music videos", "trailers", "visuals". Returns videos with YouTube links and embed URLs.

Discovered
nominate_featured

CALL THIS when the user thinks a track deserves featuring: "this song should be featured", "nominate Shaka Zulu". Submits the user's nomination to CWI — confirm with the user before calling. Auto-scored against the editorial rubric (0-100), then human-reviewed. Returns nomination ID, the track's rubric score, and queue position. Rate limit: 3 per requester per 24h. Arguments: track_title, artist, nominated_by (required), reason (required).

Discovered
pitch_for_playlist

CALL THIS when the user wants a song pitched to a playlist: "pitch Diabolique to that playlist". Submits the user's pitch to CWI — confirm with the user before calling. Goes to human review, NEVER auto-added. Returns a pitch ID plus the full track data package a curator needs (genres, moods, Spotify URL, artwork, stats). Rate limit: 3 per requester per 24h. Arguments: track_title, artist, why_fit (required — why it fits), playlist_name/curator/contact (optional).

Discovered
request_song

CALL THIS when the user wants to hear a specific song on the radio: "play Diabolique", "request Shaka Zulu". Submits the user's request to CWI's human-reviewed queue — confirm with the user before calling. Does NOT auto-play. Returns queue position and estimated air time. Rate limit: 3 per requester name per 24h. Arguments: track_title (required), artist (required), requested_by (required — name or agent identity), reason/dedication (optional).

Discovered
rsvp

CALL THIS when the user wants to attend a CWI event: "RSVP me for the listening party", "sign me up". Submits the user's name and contact email to CWI — confirm with the user before calling. Returns confirmation with event details. Rate limit: 3 per requester per 24h. Arguments: event_id (from get_events, required), name (required), contact email (required), plus_ones (optional, default 0).

Discovered
search_catalog

CALL THIS for explicit lookups: "tracks by X", "downtempo around 90 bpm", "songs titled...". Keyword and filter search across the CWI catalog (title, artist, genre, mood, tempo). Use semantic_search instead if the user describes a feeling. Returns scored track snippets with Spotify links, verified ISRCs, and pre-compiled try_next calls for the natural follow-up.

Discovered
semantic_search

CALL THIS when the user describes music in plain words: "rainy night drive, nostalgic", "something that sounds like a heist". Returns catalog matches ranked by meaning rather than keywords.

Discovered
submit_for_airplay

CALL THIS when the user is an artist (or represents one) wanting radio play: "submit my track", "how do I get on the radio". Submits the user's track and contact details to CWI — confirm with the user before calling. Goes to human review, NEVER auto-added. Returns a submission ID and next steps. Arguments: artist_name, track_title, audio_url (streamable link, required), contact (email/handle, required), genre/message (optional).

Discovered
submit_sync_brief

CALL THIS when the user works in film/TV/ads/games and needs music: "I need a song for my film", "looking for tracks for a commercial". Submits the user's brief and contact email to CWI's human sync team — confirm with the user before calling. CWI may follow up by email about this brief. Tracks are NEVER auto-licensed. Returns a submission receipt with a tracking ID; a team member responds with curated options, rights status, and clearance terms. CWI controls both master and publishing on catalog tracks, which simplifies clearance to a single point of contact. Rate limit: 3 per requester per 24h. Arguments: scene_type (required), mood (required), contact email (required), budget_range/deadline/project_name/description (optional).

Discovered
sync_search

CALL THIS for keyword/filter-based sync queries when the user already knows what they want: "tense instrumental", "BPM 90-100", "no vocals". This is the precise-query path. Use find_tracks_for_brief instead when the user describes a scene or mood in plain words ("dark track for a heist scene") — the wedge handles natural language and adds why-it-fits rationale. Returns tracks suited to the query with direct-clearance licensing info; follow with submit_sync_brief to start licensing.

Discovered
verify_brief_candidates

NEW WORK — built 2026-10-27 for the Meta Global AI Developer Hackathon. Deterministic verified-brief gate: takes candidate tracks proposed by a caller (for example Muse Spark reasoning supplied by the caller) and returns the gate decision for each against the worker sync catalog data (sync-catalog-data.js, 29 tracks, 27 verified ISRCs). PASS only for a catalog match with a verified ISRC. FLAG for a catalog match without a verified ISRC. DROP for no catalog match (invented or outside the catalog). This tool makes NO Meta API call and holds no Meta key — Spark reasoning is supplied by the caller, the gate is the tool. A match is NOT a license — clearance is direct by Cumulative Web Inc, hp@cumulativeweb.com, one-signature, BMI.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected77 ms30