Home / MCP registry index / io.github.CumulativeWebInc/cwi-discovery-engine
io.github.CumulativeWebInc/cwi-discovery-engine
io.github.CumulativeWebInc/cwi-discovery-engine in the official MCP registry.
Endpoint https://cwi-machine-data.hp-ace.workers.dev/mcp. Source: github.com/CumulativeWebInc/cwi-learn.
The registry describes it as: CWI Discovery Engine: 29-tool music catalog MCP — search, sync, Radio 365 live, chaining.
We read its 29 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
find_tracks_for_brief search_catalog get_track get_artist sync_search semantic_search get_graph get_release get_radio get_announcements get_featured get_up_next get_schedule request_song submit_for_airplay get_requests submit_sync_brief pitch_for_playlist nominate_featured get_recommendations get_events rsvp get_label get_sync_catalog get_lyrics get_press_kit get_videos get_genre get_playlists
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-cumulativewebinc-cwi-discovery-engine)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.