TrackForge MCP server
studio.trackforge/music-registration-checktrackforge.studiostreamable-httpv1.0.2Scanned
Check a catalogue against The MLC, look up a song's writers, publishers and ISWC, validate CWR files
4 tools: 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the TrackForge MCP server can do
The TrackForge MCP server is published by trackforge.studio, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: check_catalogue and request_full_report), but cannot delete data. 2 tools only read.
3 tools bring in text other people can write (lookup_recording, check_catalogue and request_full_report).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 1.0.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
check_catalogueCatalogue 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.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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, missing_from_bulk, unknown) with its confidence, MLC song code and any unclaimed share, plus a summary counting each verdict, the next step for each verdict found, and the as_of date of the MLC snapshot. Each row also lists the ISWCs and writers of the works MusicBrainz links to the recording. Invalid ISRCs are listed and skipped. It finds recordings whose music royalties may be unmatched or unclaimed. Findings from registration data, not legal advice or a statement of song ownership.
Annotations the server declares
- title: Catalogue registration check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
request_full_reportAsk for a full music royalties and registration review of a catalogue.Reads text others writeNo findings
Why it is in this group
- The name "request_full_report" says "request": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 asked for a follow-up and agreed to be contacted: consent_to_contact must be true.
Annotations the server declares
- title: Request a royalties review
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 2Show 2 read-only tools
lookup_recordingISRC lookup and music royalties registration check for one recording, with the song's rights data.Reads text others writeNo findings
Why it is in this group
- The name "lookup_recording" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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, and a verdict per recording: registered, partial (a share is unclaimed), nobody (no MLC work is linked), conflict, missing_from_bulk (an earlier copy of The MLC's bulk data showed publishers or a work link that the current copy does not; the bulk data has dropped claims that are still live, so never a finding that a share is unclaimed), or unknown. Each verdict carries dated evidence (as_of, from The MLC's bulk data snapshot) and a factual next step. Also returns what MusicBrainz records for the recording: the linked works with their ISWCs, the writers and publishers with their IPI and ISNI numbers, the earliest release's album, date, label and catalogue number, and the MusicBrainz page. With full_record true it adds every release (label, catalogue number, country and date), performer and producer credits and related recordings; that answer is many times larger. When several matches are equally likely, ambiguous is true and all are returned. Findings from registration data, not legal advice or a statement of song ownership.
Annotations the server declares
- title: Song registration check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
validate_cwrCWR validation: checks the text of a CWR 2.1 or 2.2 (Common Works Registration) file, against the version it declares.No findings
Why it is in this group
- The name "validate_cwr" says "validate": a word for reading.
Description, as the server wrote it CWR validation: checks the text of a CWR 2.1 or 2.2 (Common Works Registration) file, against the version it declares. CWR registers songs with 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 explanation and how to fix it. Pass the file content as ASCII text, up to 256 KB; larger files can be uploaded at https://trackforge.studio/cwr-tool. Validation does not guarantee acceptance by a society. The file is not stored.
Annotations the server declares
- title: CWR validation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:19 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.trackforge.studio/api/v1/mcp: tools/list returned 4 tools to an anonymous client, including check_catalogue (write), request_full_report (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:check_catalogueChanges thingsdescription
- Changed:lookup_recordingOnly readsdescription
- Changed:validate_cwrOnly readstitledescription
Tools1 changed.~1 changedView diff
- Changed:validate_cwrOnly readsinputSchema
Install
Pinned to version 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http music-registration-check https://api.trackforge.studio/api/v1/mcpclaude mcp add --transport http music-registration-check https://api.trackforge.studio/api/v1/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__music-registration-check__lookup_recording",
"mcp__music-registration-check__validate_cwr"
],
"ask": [
"mcp__music-registration-check__check_catalogue",
"mcp__music-registration-check__request_full_report"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as music-registration-check. Review it before you use it.
Capability tags behind 3 rules
- mcp__music-registration-check__lookup_recording untrusted-input
- mcp__music-registration-check__check_catalogue untrusted-input
- mcp__music-registration-check__request_full_report untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/studio.trackforge/music-registration-check/verify?hash=4cdf4fdcb58b3b265f77107ffbbf6e31b27db9642f7b583dc980fe2745dfdad5" | jq -e '.changed == false'Pinned hash 4cdf4fdcb58b, from Nov 19, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/studio.trackforge/music-registration-check/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/studio.trackforge/music-registration-check)Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.
TrackForge MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the TrackForge MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the TrackForge MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the TrackForge MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the TrackForge MCP server have?
- 4 tools: 2 write, 2 read. check_catalogue, request_full_report, lookup_recording and validate_cwr.
Does the TrackForge MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the TrackForge MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the TrackForge MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.