TrackForge
REMOTE · API.TRACKFORGE.STUDIO
Check a catalogue against The MLC, look up a song's writers, publishers and ISWC, validate CWR files
Available components
Last scanned (8 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1326 tokens (~331/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.trackforge.studio/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trackforge.studio | CN=WE1,O=Google Trust Services,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8e4e98fc9dc52111137599228ce84744 |
| SANs: trackforge.studio, *.trackforge.studio | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.trackforge.studio. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| studio. | present | 1354 | 8 | Verified |
| trackforge.studio. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none'; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.trackforge.studio/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://api.trackforge.studio/api/v1/mcp | HTTPS enforced | 301 | https://api.trackforge.studio/api/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_catalogue Catalogue registration check: up to 50 recordings against The MLC ~205
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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| isrcs | array | yes | ISRCs, 12 characters, e.g. USIR20400274 (hyphens and spaces allowed). At most 50; split larger catalogues into several calls. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| mlc_source | – | – | – |
| summary | – | yes | – |
No examples provided.
lookup_recording Song registration check: MLC registration, unclaimed shares, writers, publishers and ISWCs ~438
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, 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.
| Name | Type | Req | Description |
|---|---|---|---|
| artist | string | – | Optional artist name; only together with title. |
| full_record | boolean | – | True to add MusicBrainz's full record of the recording: every release with its label, catalogue number, country and date, the credits, and related recordings. Only for an ISRC or a Spotify link that… |
| isrc | string | – | ISRC, 12 characters, e.g. USIR20400274 (hyphens and spaces allowed). |
| spotify_url | string | – | Spotify track link (https://open.spotify.com/track/...) or spotify:track:... URI. Album and playlist links are not accepted. |
| title | string | – | Song title, when no ISRC or link is available. |
| youtube_url | string | – | YouTube video link; resolved from the video title, so matches are low confidence. |
| Name | Type | Req | Description |
|---|---|---|---|
| ambiguous | boolean | – | – |
| candidates | array | – | – |
| input_kind | – | yes | – |
| mlc_source | – | – | – |
| notes | array | – | – |
| query | – | yes | – |
| results | array | – | – |
No examples provided.
request_full_report Request a music royalties review (a person follows up) ~212
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.
| Name | Type | Req | Description |
|---|---|---|---|
| catalogue_description | string | – | Free-text description of the catalogue, e.g. artist names, number of songs, territories. |
| consent_to_contact | boolean | yes | True only if the user has agreed that TrackForge may contact them by email about this request. |
| string | yes | Contact email address for the follow-up. | |
| isrcs | array | – | ISRCs in the catalogue (up to 200). Give isrcs, catalogue_description, or both. |
| name | string | yes | Contact name. |
| organisation | string | – | Optional label, publisher or company name. |
| Name | Type | Req | Description |
|---|---|---|---|
| follow_up | string | yes | – |
| isrcs_not_recognised | array | – | – |
| isrcs_recorded | integer | yes | – |
| recorded | boolean | yes | – |
| reference | string | yes | – |
| report_generated | boolean | – | – |
No examples provided.
validate_cwr CWR validation (CWR 2.1 file check) ~211
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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| cwr_text | string | yes | The full CWR file content (ASCII text, HDR to TRL). |
| filename | string | – | Optional original filename, e.g. CW260001TF_000.V21. A society receiver code in the name selects that society's rules. |
| recipient_profile | string | – | Which society's rules to apply; cisac_base when unsure. |
| Name | Type | Req | Description |
|---|---|---|---|
| error_count | integer | yes | – |
| full_report | string | yes | – |
| is_valid | boolean | yes | – |
| issues | array | yes | – |
| issues_total | integer | yes | – |
| issues_truncated | boolean | yes | – |
| line_endings_converted | boolean | yes | – |
| recipient_profile | string | yes | – |
| recipient_resolution | object | yes | – |
| record_count | integer | yes | – |
| spec_version | string | yes | – |
| status_dimensions | – | – | – |
| stored | boolean | – | – |
| transaction_count | integer | yes | – |
| warning_count | integer | yes | – |
No examples provided.
How do I install the TrackForge MCP server?
TrackForge is a hosted endpoint at https://api.trackforge.studio/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.trackforge.studio
claude mcp add --transport http studio-trackforge-music-registration-check 'https://api.trackforge.studio/api/v1/mcp'
What is the TrackForge MCP server?
TrackForge is an MCP server listed in the public MCP registry as studio.trackforge/music-registration-check. Check a catalogue against The MLC, look up a song's writers, publishers and ISWC, validate CWR files. This page covers its hosted endpoint (https://api.trackforge.studio/api/v1/mcp).
Is the TrackForge MCP server safe to use?
TrackForge scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TrackForge MCP server expose?
TrackForge exposes 4 tools: lookup_recording, check_catalogue, validate_cwr, request_full_report. Their descriptions and schemas cost roughly 1,066 tokens of context every time the server is loaded.
Does the TrackForge MCP server require authentication?
No. We connected to TrackForge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TrackForge MCP server still maintained?
TrackForge is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.