studio.trackforge/music-registration-check · v1.0.2 · ai-and-media
TrackForge is healthy: it completed an MCP handshake in 2411 ms and exposes 4 tools.
Check a catalogue against The MLC, look up a song's writers, publishers and ISWC, validate CWR files
Endpoint: https://api.trackforge.studio/api/v1/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 4 |
| Latency | 2411 ms |
| Last checked (UTC) | 2026-10-16T20:20:41.129Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-16T20:20:41.129Z | Healthy | 2411 | |
| 2026-10-15T13:40:08.023Z | Healthy | 1820 |
lookup_recording | ISRC lookup and music royalties registration check for one recording, with the song's rights data. Give exactly one of: an ISRC, a Spotify track link, a song title (optionally with the artist), or a YouTube link. Returns candidate recordings and MLC works, how each was matched and how confidently, a |
check_catalogue | Catalogue registration check (batch ISRC lookup): checks up to 50 recordings at once against The MLC's bulk data (US mechanical royalties), and a larger catalogue in several calls. Returns each recording's verdict (registered, partial, nobody, conflict, unknown) with its confidence, MLC song code an |
validate_cwr | CWR validation: checks the text of a CWR 2.1 (Common Works Registration) file used to register songs with music royalties societies such as The MLC, PRS for Music / ICE, SACEM or CMRRA. Returns whether the file is valid, error and warning counts, and each issue with its line, rule, plain-language ex |
request_full_report | Ask for a full music royalties and registration review of a catalogue. Records the request (contact name, email, optional organisation, the catalogue's ISRCs and/or a description) so a person at TrackForge can follow up by email. It does not generate or send a report. Call it only when the user has |