TrackForge

npx add-mcp 'https://api.trackforge.studio/api/v1/mcp'

What it does

• Check a catalogue against The MLC. Give it your ISRCs, up to 50 a request. For each recording it says whether The MLC links it to a work and whether a share is unclaimed, and it counts each result. That shows where US mechanical royalties may be going unmatched or unclaimed.
• Look up one song. One ISRC, Spotify link or title. It returns the recording’s MLC verdict and, from MusicBrainz, the song’s ISWCs, songwriters and publishers with their IPI numbers, and its first release.
• Validate a CWR file. Paste the CWR 2.1 file you are about to send to a society. It reports every error and warning with the line, the rule and how to fix it. Files up to 256 KB; larger files go through the CWR Workbench.
• Ask for a person. If you want someone at TrackForge to look at your catalogue, say so and agree to be contacted. Your name and email address are recorded and a person replies by email. Nothing is sent automatically.

What you can ask

Real answers from the server, shortened. Your assistant puts them in its own words.

Check my catalogue against The MLC. How many of these recordings have no linked work, and how many have unclaimed shares?

Checked

300 recordings

No linked work

102

Unclaimed share

67

Registered, nothing unclaimed

111

MLC data as of

29 September 2026

From a sample of 300 recordings, not a client’s catalogue. Each recording also gets its own verdict.

Here is the CWR file I am about to send. Is it valid, and what should I fix?

Result

Not valid: 1 error and 1 warning in 1 transaction

Line 3, error

Work title is blank. Every NWR/REV record must have a non-empty work title (positions 20-79).

Line 4, warning

Publisher IPI Name # fails its check digits. That normally means a typo or a transposed digit.

A test file with its title removed. A valid result does not guarantee that a society will accept the file.

Is ISRC USIR20400274 registered with The MLC, and is any share unclaimed?

Verdict

registered, high confidence

Evidence

Linked to MLC work M1972U, “MR. BRIGHTSIDE”, ISWC T0721040692

MLC data as of

29 September 2026

Who wrote the song on that recording, and which label first released it?

Writers

Brandon Flowers and Dave Keuning, each with an IPI number

Publishers

The Killers Publishing; Universal Music Publishing Ltd.

First release

“Mr. Brightside”, 29 September 2003, Lizard King Records, catalogue number LIZARD007X

Source

MusicBrainz

How to read a verdict

Every recording gets one of five verdicts. An MLC answer always carries the date its data is true as of, and a next step when there is something to do.

registered

Linked to one MLC work, with nothing unclaimed or in dispute.

partial

Linked to one MLC work, and a share is unclaimed or in dispute.

nobody

No MLC work is linked to the recording. The answer says whether to match it to an existing work or register one.

conflict

Linked to more than one MLC work.

unknown

The data could not be read. Never a negative finding.

Having a publisher does not mean your songs are registered

A publisher or administrator on record shows a relationship, not a finished registration. The MLC pays US mechanical royalties from streaming and download services only when a recording is linked to a registered work with its shares claimed. This server checks that link, recording by recording.

How to add it

Any AI assistant

Look in your assistant’s settings for connectors, integrations, tools or MCP servers, and add a custom one with these three settings.

Address

https://api.trackforge.studio/api/v1/mcp

Connection type

Streamable HTTP. Some assistants call it a remote MCP server or an HTTP server.

Sign-in

None. Leave any sign-in, OAuth or API key field empty.

Steps for the assistants TrackForge has tested are below.

Claude

Tested 3 October 2026 on claude.ai.

1. In Claude, open Customize, then Connectors.
2. Select Add, then Add custom connector.
3. Give it a name, such as TrackForge, paste the server address and select Continue. Claude shows No sign-in as detected. Select Add.
4. On the connector’s page, select Connect.
5. Ask your question in a new conversation. The first time each tool is used, Claude asks whether to allow it.

Custom connectors are available on Free, Pro and Max plans; the Free plan allows one. On Team and Enterprise plans an Owner adds it under Organization settings, Connectors, and members then select Connect.

ChatGPT

Tested 5 October 2026 on chatgpt.com.

1. In ChatGPT, open Settings, then Security and login, and turn on Developer mode.
2. Open Plugins, select the plus button, then Create custom MCP server, then Create MCP App.
3. Give it a name, such as TrackForge, paste the server address and set Authentication to No Auth.
4. Tick “I understand and want to continue”, select Create, then Connect.
5. In a new conversation, select the plus button, type TrackForge and choose it. Then ask your question.

Developer mode was available on a Free plan when tested; OpenAI lists it for Plus, Pro, Business, Enterprise and Education accounts. To have a list of recordings checked together, ask for the catalogue check by name.

Command-line assistants

Tested: Claude Code on 3 October 2026 and Codex CLI on 5 October 2026.

One command adds the server.

Claude Code:

claude mcp add --transport http trackforge https://api.trackforge.studio/api/v1/mcp

Codex CLI:

codex mcp add trackforge --url https://api.trackforge.studio/api/v1/mcp

Limits and privacy

Free. One conversation can check up to 600 recordings every five minutes and 6,000 a day. A catalogue request takes up to 50 recordings and a CWR file up to 256 KB.

Each call is logged for usage measurement: the tool, the kind of input, the ISRCs, the outcome and the assistant’s name, with a one-way hash of the address rather than the address itself. Titles, artist names and CWR file content are not logged. Contact details are stored only when you ask for a follow-up. Privacy Policy · Terms of Service

What it is not

• Answers are findings from registration data as of the date shown. They are not legal advice and not a statement of who owns a song or who may use a recording.
• The registration check reads The MLC’s data, which covers US mechanical royalties. It holds no PRS for Music, PPL or SoundExchange data.
• Writer, publisher, ISWC and release details come from MusicBrainz’s public-domain core data, which its community edits: evidence, not proof.
• A Spotify link is used only to find the recording’s ISRC. Spotify’s own data is not returned.
• TrackForge is independent of Anthropic, OpenAI, The MLC, MusicBrainz and Spotify, and none of them endorses this server.

Questions

How do I check a catalogue against The MLC with an AI assistant?

Add the TrackForge MCP server (https://api.trackforge.studio/api/v1/mcp) to your assistant, give it the catalogue’s ISRCs and ask how many recordings have no linked work and how many have an unclaimed share. Each request takes up to 50 ISRCs and returns a verdict for every recording, a count of each verdict and the date the MLC data is true as of. One conversation can check up to 600 recordings every five minutes.

What is the TrackForge MCP server?

A free remote MCP (Model Context Protocol) server at https://api.trackforge.studio/api/v1/mcp. It gives an AI assistant three checks: a catalogue registration check against The MLC’s data, a song lookup by ISRC, Spotify link or title that returns the song’s ISWCs, writers and publishers, and CWR 2.1 file validation. A fourth tool lets you ask a person at TrackForge to follow up. Answers are findings from registration data, not legal advice and not a statement of who owns a song. No account or API key is needed.

Can it check a CWR file before I send it?

Yes. Paste the text of a CWR 2.1 file, up to 256 KB, and ask whether it is valid. The answer lists each error and warning with its line, the rule it breaks and how to fix it. A valid result does not guarantee that a society will accept the file. Larger files go through the CWR Workbench at trackforge.studio/cwr-tool.

Which AI assistants can use it?

Any assistant or app that can add a remote MCP server by its address: it uses the open Model Context Protocol over Streamable HTTP and needs no sign-in. Tested with Claude and Claude Code on 3 October 2026, and with ChatGPT and Codex CLI on 5 October 2026.

How do I check whether a song is registered with The MLC using Claude?

Add https://api.trackforge.studio/api/v1/mcp as a custom connector in Claude under Customize, Connectors, then ask with an ISRC, a Spotify track link or a song title. The answer gives a verdict (registered, partial, nobody, conflict or unknown), the date the MLC data is true as of, and a next step when there is one.

Where does the data come from, and how current is it?

MLC answers come from TrackForge’s copy of The MLC’s public bulk data, refreshed weekly, and every answer carries the snapshot date. Writer, publisher, ISWC and release details come from TrackForge’s copy of MusicBrainz’s public-domain core data, refreshed about twice a month. The server never queries The MLC live.

Help and documentation

• MCP server documentation: Every tool, input and limit, and how to read each verdict.
• auth.md: The same details in a form for automated clients.
• ISRC Lookup: The same checks in your browser, with CSV and PDF export.
• CWR Workbench: Create, check and read CWR files in the browser, including files over 256 KB.
• Support: How to read an answer, and who to contact.
• Registry entry: The server’s description for MCP registries: studio.trackforge/music-registration-check.
• ISRC Registration Gaps: How the gap between Spotify coverage and MLC work registration leaves mechanical royalties unpaid.
• The Unclaimed Economy: Works with unclaimed US mechanical royalties at The MLC, cross-referenced against other sources.
• What is CWR?: The Common Works Registration format, and how a work reaches a society.

{ "@context": "https://schema.org", "@type": "Organization", "@id": "https://trackforge.studio/#org", "name": "TrackForge", "url": "https://trackforge.studio", "logo": "https://trackforge.studio/favicon-512x512.png", "description": "The registration-truth layer for music rights. TrackForge finds out what's actually registered, fixes what's broken, and proves it's paying.", "foundingDate": "2025", "sameAs": [ "https://www.wikidata.org/wiki/Q138637747", "https://www.linkedin.com/company/trackforge-rights-rating/", "https://x.com/RightsRating", "https://github.com/James-AdaptIntel" ], "contactPoint": { "@type": "ContactPoint", "contactType": "Sales", "email": "hello@trackforge.studio" }, "areaServed": "Worldwide", "knowsAbout": [ "Music catalogue valuation", "Rights management", "Metadata certification", "Due diligence", "Royalty recovery", "Music publishing", "Performing rights organisations" ] }
{ "@context": "https://schema.org", "@type": "Service", "name": "TrackForge Rating Certification", "provider": { "@type": "Organization", "name": "TrackForge", "url": "https://trackforge.studio" }, "description": "Cryptographically verifiable music catalogue rating certification. TrackForge applies the published AAA-D methodology, constructs Merkle roots from certified snapshots, and timestamps proof state through OpenTimestamps and Bitcoin anchoring.", "serviceType": "Rights Rating Certification", "areaServed": "Worldwide", "url": "https://trackforge.studio/docs/certification/", "documentation": "https://trackforge.studio/docs/certification/overview/what-is-certification", "termsOfService": "https://trackforge.studio/terms" }
{ "@context": "https://schema.org", "@type": "WebSite", "@id": "https://trackforge.studio/#website", "name": "TrackForge", "url": "https://trackforge.studio", "description": "The registration-truth layer for music rights. We find out what's actually registered, fix what's broken, and prove it's paying.", "publisher": { "@type": "Organization", "@id": "https://trackforge.studio/#org", "name": "TrackForge", "url": "https://trackforge.studio" } }
{"@context":"https://schema.org","@type":"SoftwareApplication","name":"TrackForge MCP server","alternateName":["Music royalties registration check for AI assistants","CWR validation MCP server","ISRC lookup MCP server"],"description":"Ask your AI assistant which catalogue recordings have no MLC work or an unclaimed share, and whether a CWR file is valid. Free MCP server with ISRC lookup.","url":"https://trackforge.studio/mcp","applicationCategory":"MusicApplication","applicationSubCategory":"MCP server for music registration data","operatingSystem":"Any","isAccessibleForFree":true,"inLanguage":"en","datePublished":"2026-10-03","dateModified":"2026-10-07","image":"https://trackforge.studio/og-card.png","softwareHelp":{"@type":"CreativeWork","url":"https://trackforge.studio/docs/ai-assistants/mcp-server"},"featureList":["Catalogue registration check: up to 50 recordings a request against The MLC’s data, with a count of each verdict","Song lookup by ISRC, Spotify link or title: MLC verdict, ISWCs, songwriters and publishers with IPI numbers","CWR 2.1 file validation with each error and warning, its line and how to fix it","No account or API key"],"offers":{"@type":"Offer","price":"0","priceCurrency":"GBP"},"provider":{"@type":"Organization","name":"TrackForge","url":"https://trackforge.studio","logo":{"@type":"ImageObject","url":"https://trackforge.studio/favicon-512x512.png"}}}
{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"How do I check a catalogue against The MLC with an AI assistant?","acceptedAnswer":{"@type":"Answer","text":"Add the TrackForge MCP server (https://api.trackforge.studio/api/v1/mcp) to your assistant, give it the catalogue’s ISRCs and ask how many recordings have no linked work and how many have an unclaimed share. Each request takes up to 50 ISRCs and returns a verdict for every recording, a count of each verdict and the date the MLC data is true as of. One conversation can check up to 600 recordings every five minutes."}},{"@type":"Question","name":"What is the TrackForge MCP server?","acceptedAnswer":{"@type":"Answer","text":"A free remote MCP (Model Context Protocol) server at https://api.trackforge.studio/api/v1/mcp. It gives an AI assistant three checks: a catalogue registration check against The MLC’s data, a song lookup by ISRC, Spotify link or title that returns the song’s ISWCs, writers and publishers, and CWR 2.1 file validation. A fourth tool lets you ask a person at TrackForge to follow up. Answers are findings from registration data, not legal advice and not a statement of who owns a song. No account or API key is needed."}},{"@type":"Question","name":"Can it check a CWR file before I send it?","acceptedAnswer":{"@type":"Answer","text":"Yes. Paste the text of a CWR 2.1 file, up to 256 KB, and ask whether it is valid. The answer lists each error and warning with its line, the rule it breaks and how to fix it. A valid result does not guarantee that a society will accept the file. Larger files go through the CWR Workbench at trackforge.studio/cwr-tool."}},{"@type":"Question","name":"Which AI assistants can use it?","acceptedAnswer":{"@type":"Answer","text":"Any assistant or app that can add a remote MCP server by its address: it uses the open Model Context Protocol over Streamable HTTP and needs no sign-in. Tested with Claude and Claude Code on 3 October 2026, and with ChatGPT and Codex CLI on 5 October 2026."}},{"@type":"Question","name":"How do I check whether a song is registered with The MLC using Claude?","acceptedAnswer":{"@type":"Answer","text":"Add https://api.trackforge.studio/api/v1/mcp as a custom connector in Claude under Customize, Connectors, then ask with an ISRC, a Spotify track link or a song title. The answer gives a verdict (registered, partial, nobody, conflict or unknown), the date the MLC data is true as of, and a next step when there is one."}},{"@type":"Question","name":"Where does the data come from, and how current is it?","acceptedAnswer":{"@type":"Answer","text":"MLC answers come from TrackForge’s copy of The MLC’s public bulk data, refreshed weekly, and every answer carries the snapshot date. Writer, publisher, ISWC and release details come from TrackForge’s copy of MusicBrainz’s public-domain core data, refreshed about twice a month. The server never queries The MLC live."}}]}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"TrackForge","item":"https://trackforge.studio"},{"@type":"ListItem","position":2,"name":"MCP server","item":"https://trackforge.studio/mcp"}]}