io.github.CumulativeWebInc/cwi-discovery-engine
REMOTE · CWI-MACHINE-DATA.HP-ACE.WORKERS.DEV
CWI Discovery Engine: 29-tool music catalog MCP — search, sync, Radio 365 live, chaining.
Available components
Last scanned (10 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Entertainment and Games
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4385 tokens (~132/item across 33 items; 30 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 30 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 32 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- New tool “verify_brief_candidates” functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://cwi-machine-data.hp-ace.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hp-ace.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5e171f935f8b64c1a292295e3a561cae3de |
| SANs: *.hp-ace.workers.dev, hp-ace.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cwi-machine-data.hp-ace.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cwi-machine-data.hp-ace.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://cwi-machine-data.hp-ace.workers.dev/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_tracks_for_brief Find Tracks for a Brief ~241
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | string | yes | Natural-language music brief, e.g. "tense instrumental for a heist scene". Truncated at 500 characters. |
| explicit | boolean | – | true = explicit only, false = non-explicit only. Omit for all. |
| limit | number | – | Max tracks to return, 1-5 (default 3). |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| brief | string | yes | – |
| clearance_summary | string | yes | Plain-language clearance status for the matched tracks: who controls master+publishing, one-signature terms, PRO. |
| count | integer | yes | – |
| generated_at | string | – | – |
| licensing_disclaimer | string | yes | States that a match is not a license grant. |
| next_steps | array | yes | Concrete actions: submit_sync_brief with the brief, contact email, license terms URL. |
| tokens | array | – | – |
| tracks | array | yes | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
get_announcements Get Announcements ~113
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".
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional filter: "releases", "news", or "events". Omit for all categories. |
| limit | number | – | Max announcements to return, 1-50 (default 10). |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| announcements | array | yes | – |
| category | string | – | – |
| count | integer | yes | – |
| data_updated_at | string|null | – | – |
| generated_at | string | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
get_artist Get Artist Profile ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Artist name, e.g. "That Boy Hi Hat". |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| artist | string | yes | – |
| related_nodes | array | – | Up to 8 connected knowledge-graph node IDs. |
| track_count | integer | yes | – |
| tracks | array | yes | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
get_events Get Events ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| upcoming_only | boolean | – | Only show upcoming events (default true). Set false to see all. |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| count | integer | yes | – |
| events | array | yes | – |
| generated_at | string | – | – |
| note | string | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
| upcoming_only | boolean | – | – |
No examples provided.
get_featured Get Featured Tracks ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max tracks to return, 1-20 (default 10). |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| count | integer | yes | – |
| data_updated_at | string|null | – | – |
| featured | array | yes | – |
| generated_at | string | – | – |
| new_release_spotlight | object | – | Active pre-release spotlight: title, artist, drop date, presave URL, ISRC. |
| rotation | string|null | – | – |
| rotation_raw | string|null | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
get_genre Get Genre Info ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| genre | string | yes | Genre name, e.g. "post-trap futurism" (required). |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| available_genres | array | – | – |
| found | boolean | yes | – |
| genre | object|string | – | – |
| ok | boolean | yes | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
get_graph Get Catalog Graph ~74
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| full_graph | string | yes | – |
| generated_at | string | – | – |
| source | string | yes | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
get_label Get Label Profile ~52
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| label | object | yes | – |
| ok | boolean | yes | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
get_lyrics Get Lyrics ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| track_id | string | yes | Track ID from get_track or search_catalog (required). |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| found | boolean | yes | – |
| lyrics | object | – | – |
| note | string | – | – |
| ok | boolean | yes | – |
| track_id | string | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
get_playlists Get Playlists ~67
CALL THIS when the user asks where CWI tracks are placed: "what playlists", "where is Diabolique placed". Returns verified playlist placements only.
| Name | Type | Req | Description |
|---|---|---|---|
| artist | string | – | Optional: filter by artist name. |
| track_id | string | – | Optional: filter by track ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| count | integer | yes | – |
| label_playlists | array | – | – |
| note | string | – | – |
| ok | boolean | yes | – |
| placements | array | yes | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
get_press_kit Get Press Kit ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| artist | string | – | Optional: specific artist name for their press bio. |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| ok | boolean | yes | – |
| press_kit | object | yes | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
get_radio Get Radio Status ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include | string | – | Optional comma-separated sections to include: "now_playing", "listeners", "stream". Omit or pass "all" for everything. Unknown values are ignored. |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| generated_at | string | – | – |
| listeners | object | – | – |
| now_playing | object | – | – |
| proof_of_airplay | object | – | – |
| station | string | yes | – |
| station_url | string | yes | – |
| stream | object | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
get_recommendations Get Music Recommendations ~254
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).
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of recommendations, 1-10 (default 5). |
| genre_filter | string | – | Optional genre filter (e.g. "trap", "afrobeats", "rap rock"). |
| vibe_description | string | yes | Describe the vibe/mood you want music for. |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| count | integer | yes | – |
| generated_at | string | – | – |
| genre_filter | string|null | – | – |
| method | string | yes | – |
| new_release_spotlight | object|null | – | – |
| note | string | – | – |
| recommendations | array | yes | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
| vibe_description | string | yes | – |
No examples provided.
get_release Get Release Info ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Release id, e.g. "cyberpunk-2027". Omit for the latest release. |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| found | boolean | yes | – |
| id | string | yes | – |
| known_releases | array | – | – |
| new_release_spotlight | object | – | Active pre-release spotlight: title, artist, drop date, presave URL, ISRC. |
| packet | object | – | Fact packet: facts list of {claim, evidence{source, observed}, tier}. |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
get_requests Get Song Requests ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max requests to return, 1-20 (default 10). |
| status | string | – | Filter by status: "pending" (awaiting review), "played" (aired), "all". Default "pending". |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| count | integer | yes | – |
| generated_at | string | – | – |
| note | string | – | – |
| pending_count | integer | – | – |
| requests | array | yes | – |
| station | string | yes | – |
| status_filter | string | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
get_schedule Get Radio Schedule ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Date for the schedule in YYYY-MM-DD format. Defaults to today (UTC). |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| date | string | – | – |
| generated_at | string | – | – |
| note | string | – | – |
| period_seconds | number|null | – | – |
| program_version | string|null | – | – |
| slot_count | integer | yes | – |
| slots | array | yes | – |
| station | string | yes | – |
| stream_url | string | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
get_sync_catalog Get Sync Catalog ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| genre | string | – | Filter by genre, e.g. "post-trap futurism". |
| mood | string | – | Filter by mood, e.g. "dark", "energetic". |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| count | integer | yes | – |
| note | string | – | – |
| ok | boolean | yes | – |
| tracks | array | yes | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
get_track Get Track Details ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id_or_title | string | yes | Track title (exact or partial) or a Spotify track ID / open.spotify.com URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| album | string|null | – | – |
| apple_music_url | string | – | – |
| artist | string | yes | – |
| artist_mbid | string|null | – | MusicBrainz artist MBID. |
| artwork_url | string|null | – | – |
| contexts | array | – | – |
| credits | object|null | – | – |
| description | string | – | 150-300 word NLP prose (Whisper-derived where flagged; not proofread). |
| engineer | string|null | – | – |
| featured | boolean | – | – |
| genres | array | – | – |
| graph_node | string | – | – |
| isrc | string|null | – | – |
| label | string|null | – | – |
| mbid | string|null | – | MusicBrainz recording MBID. |
| moods | array | – | – |
| presave_url | string|null | – | – |
| producers | array | – | – |
| related_nodes | array | – | Up to 8 connected knowledge-graph node IDs. |
| release_date | string|null | – | Original commercial release date (YYYY-MM-DD). |
| scenes | array | – | – |
| signature | object|null | – | That Boy Hi Hat flow-architecture signature block (present on his tracks). |
| sounds_like_lanes | array | – | – |
| spotify_url | string | – | – |
| streaming_urls | object|null | – | – |
| studio | string|null | – | – |
| summary_markdown | string | – | Compact markdown: title, ISRC/UPC, studio, genres/moods, one-line sync clearance. |
| title | string | yes | – |
| track_id | string | yes | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
| upc | string|null | – | – |
| use_cases | array | – | – |
No examples provided.
get_up_next Get Up Next on Radio ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of upcoming tracks to return, 1-10 (default 5). |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| count | integer | – | – |
| generated_at | string | – | – |
| note | string | – | – |
| now_playing | object | yes | – |
| program_version | string|null | – | – |
| station | string | yes | – |
| stream_url | string | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
| up_next | array | yes | – |
No examples provided.
get_videos Get Videos ~76
CALL THIS when the user wants video content: "music videos", "trailers", "visuals". Returns videos with YouTube links and embed URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| artist | string | – | Optional: filter by artist name. |
| type | string | – | Optional: filter by type (trailer, music-video, visualizer, live). |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| count | integer | yes | – |
| ok | boolean | yes | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
| videos | array | yes | – |
No examples provided.
nominate_featured Nominate Featured Track ~165
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).
| Name | Type | Req | Description |
|---|---|---|---|
| artist | string | yes | Artist name. |
| nominated_by | string | yes | Your name or agent identity (required). |
| reason | string | yes | Why this track deserves the featured rotation (required). |
| track_title | string | yes | Title of the track you are nominating. |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| artist | string | – | – |
| graph_node | string|null | – | – |
| in_current_rotation | boolean | – | – |
| nominated_by | string | – | – |
| nomination_id | integer|null | yes | – |
| ok | boolean | yes | – |
| queue_position | integer | – | – |
| receipt | object | – | Confirmation receipt; id is the real intake row id. |
| review | string | – | – |
| rubric_note | string | – | – |
| rubric_score | number|null | – | – |
| status | string | yes | – |
| submitted_at | string | – | – |
| track_title | string | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
pitch_for_playlist Pitch for Playlist ~197
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).
| Name | Type | Req | Description |
|---|---|---|---|
| artist | string | yes | Artist name. |
| contact | string | – | Optional: email for follow-up. |
| curator | string | – | Optional: curator name or handle. |
| playlist_name | string | – | Optional: target playlist name. |
| track_title | string | yes | Title of the track you are pitching. |
| why_fit | string | yes | Why this track fits the playlist (required). |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| artist | string | – | – |
| curator | string|null | – | – |
| note | string | – | – |
| ok | boolean | yes | – |
| pitch_id | integer|null | yes | – |
| playlist_name | string|null | – | – |
| receipt | object | – | Confirmation receipt; id is the real intake row id. |
| review | string | – | – |
| status | string | yes | – |
| submitted_at | string | – | – |
| track_data | object|null | – | – |
| track_title | string | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
| why_fit | string | – | – |
No examples provided.
request_song Request a Song ~184
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).
| Name | Type | Req | Description |
|---|---|---|---|
| artist | string | yes | Artist name. |
| dedication | string | – | Optional: who this request is dedicated to. |
| reason | string | – | Optional: why you want to hear this track. |
| requested_by | string | yes | Your name or agent identity (used for rate limiting). |
| track_title | string | yes | Title of the track you want to hear. |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| artist | string | – | – |
| estimated_air_in_minutes | integer | – | – |
| ok | boolean | yes | – |
| queue_position | integer | – | – |
| request_id | integer|null | yes | – |
| requested_at | string | – | – |
| requested_by | string | – | – |
| review | string | – | – |
| status | string | yes | – |
| track_title | string | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
rsvp RSVP to Event ~157
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).
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | yes | Email for confirmation (required). |
| event_id | string | yes | Event ID from get_events (required). |
| name | string | yes | Your name (required). |
| plus_ones | number | – | Number of additional guests (default 0). |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| confirmation | string | – | – |
| event_id | string | – | – |
| event_title | string | – | – |
| name | string | – | – |
| ok | boolean | yes | – |
| plus_ones | integer | – | – |
| rsvp_at | string | – | – |
| rsvp_id | integer|null | yes | – |
| status | string | yes | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
search_catalog Search Catalog ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max tracks to return, 1-10 (default 5). |
| q | string | yes | Search keywords, e.g. "cyberpunk rap" or "dark cinematic". Truncated at 500 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| count | integer | yes | – |
| generated_at | string | – | – |
| limit | integer | – | – |
| new_release_spotlight | object | – | Active pre-release spotlight: title, artist, drop date, presave URL, ISRC. |
| query | string | yes | – |
| results | array | yes | – |
| tokens | array | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
semantic_search Semantic Music Search ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results, 1-20 (default 5). |
| q | string | yes | Natural-language music query, e.g. "dark cyberpunk rap for a film scene". Truncated at 500 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| count | integer | yes | – |
| dim | integer | – | – |
| fallback | boolean | – | – |
| fallback_note | string | – | – |
| generated_at | string | – | – |
| limit | integer | – | – |
| method | string | yes | cosine:<model> or fallback:keyword. |
| model | string | – | – |
| query | string | yes | – |
| results | array | yes | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
submit_for_airplay Submit for Airplay ~188
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).
| Name | Type | Req | Description |
|---|---|---|---|
| artist_name | string | yes | Artist name. |
| audio_url | string | yes | Streamable URL to the track audio (required for review). |
| contact | string | yes | Email or social handle for follow-up. |
| genre | string | – | Genre of the track. |
| message | string | – | Optional pitch: why this track fits Radio 365. |
| track_title | string | yes | Track title. |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| artist_name | string | – | – |
| genre | string|null | – | – |
| ok | boolean | yes | – |
| review_note | string | – | – |
| status | string | yes | – |
| submission_id | integer|null | yes | – |
| submitted_at | string | – | – |
| track_title | string | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
| what_happens_next | string | – | – |
No examples provided.
submit_sync_brief Submit Sync Brief ~304
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).
| Name | Type | Req | Description |
|---|---|---|---|
| budget_range | string | – | Optional budget range (e.g. "$1k-5k", "$10k+"). |
| contact | string | yes | Email for follow-up (required). |
| deadline | string | – | Optional deadline in YYYY-MM-DD format. |
| description | string | – | Optional: more detail about the project or scene. |
| mood | string | yes | Mood/energy needed (e.g. "dark aggressive", "uplifting anthemic"). |
| project_name | string | – | Optional project/film/show name. |
| scene_type | string | yes | Type of scene needing music (e.g. "car chase", "romantic montage"). |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| brief_id | integer|null | yes | – |
| budget_range | string|null | – | – |
| deadline | string|null | – | – |
| license_block | string | – | Markdown licensing summary: rights holders, clearance terms, contact. |
| mood | string | – | – |
| ok | boolean | yes | – |
| project_name | string|null | – | – |
| rights_note | string | – | – |
| scene_type | string | – | – |
| status | string | yes | – |
| submitted_at | string | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
| what_happens_next | string | – | – |
No examples provided.
sync_search Search Sync Catalog ~211
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bpm_max | number | – | Maximum BPM (inclusive). |
| bpm_min | number | – | Minimum BPM (inclusive). |
| explicit | boolean | – | true = explicit only, false = non-explicit only. Omit for all. |
| mood | string | – | Mood filter, matched against moods + energy words, e.g. "aggressive". |
| q | string | yes | Sync query, e.g. "club scene" or "dark aggressive". Truncated at 500 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| count | integer | yes | – |
| descriptor_provenance | string | – | – |
| filters_applied | object | – | – |
| generated_at | string | – | – |
| license_block | string | – | Markdown licensing summary for the top hit: ISRC, rights holders, clearance terms, contact. |
| query | string | yes | – |
| results | array | yes | – |
| tokens | array | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
No examples provided.
verify_brief_candidates Verify Brief Candidates ~220
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.
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | Proposed candidates, up to 50: each {title, artist}. Title matching is case-insensitive and punctuation-insensitive; the artist is echoed, not used for matching. |
| Name | Type | Req | Description |
|---|---|---|---|
| _session | object | – | Chain session: pass _session.session_token back in the next call to continue the chain. |
| built | string | – | Build date of this new tool: 2026-10-27 (Meta hackathon new work). |
| clearance_note | string | yes | – |
| counts | object | yes | – |
| decisions | array | yes | – |
| gate_source | string | – | – |
| generated_at | string | – | – |
| rule | string | – | – |
| tool | string | yes | – |
| tracks_on_file | integer | – | – |
| try_next | array | – | Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload. |
| verified_on_file | integer | – | – |
| verified_shortlist | array | yes | – |
No examples provided.
How do I install the io.github.CumulativeWebInc/cwi-discovery-engine MCP server?
io.github.CumulativeWebInc/cwi-discovery-engine is a hosted endpoint at https://cwi-machine-data.hp-ace.workers.dev/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.
remote · cwi-machine-data.hp-ace.workers.dev
claude mcp add --transport http cumulativewebinc-cwi-discovery-engine 'https://cwi-machine-data.hp-ace.workers.dev/mcp'
What is the io.github.CumulativeWebInc/cwi-discovery-engine MCP server?
io.github.CumulativeWebInc/cwi-discovery-engine is an MCP server listed in the public MCP registry as io.github.CumulativeWebInc/cwi-discovery-engine. CWI Discovery Engine: 29-tool music catalog MCP, search, sync, Radio 365 live, chaining. This page covers its hosted endpoint (https://cwi-machine-data.hp-ace.workers.dev/mcp).
Is the io.github.CumulativeWebInc/cwi-discovery-engine MCP server safe to use?
io.github.CumulativeWebInc/cwi-discovery-engine scores 79 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 io.github.CumulativeWebInc/cwi-discovery-engine MCP server expose?
io.github.CumulativeWebInc/cwi-discovery-engine exposes 30 tools: find_tracks_for_brief, search_catalog, get_track, get_artist, sync_search, and 25 more. Their descriptions and schemas cost roughly 3,981 tokens of context every time the server is loaded.
Does the io.github.CumulativeWebInc/cwi-discovery-engine MCP server require authentication?
No. We connected to io.github.CumulativeWebInc/cwi-discovery-engine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.CumulativeWebInc/cwi-discovery-engine MCP server still maintained?
io.github.CumulativeWebInc/cwi-discovery-engine is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.CumulativeWebInc/cwi-discovery-engine MCP server?
VerifyMCP ran 13 checks on io.github.CumulativeWebInc/cwi-discovery-engine, 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.