TrackForge
by trackforge.studio in Documents & files
Check a catalogue against The MLC, look up a song's writers, publishers and ISWC, validate CWR files
https://api.trackforge.studio/api/v1/mcp
Last 30 days
- Uptime
- 100%
- Response time
- 222 ms typical, 222 ms slowest 5%
- Last check
- 2 h ago
- Next check
- in 4 h
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"trackforge": {
"type": "http",
"url": "https://api.trackforge.studio/api/v1/mcp"
}
}
}4 tools
- 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 an
- 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 confiden
- 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, rul
- 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 onl
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 2 h ago | Passed | 200 | 217 ms |
| 11 h ago | Passed | 200 | 222 ms |
| 21 h ago | Passed | 200 | 276 ms |