# TrackForge (remote · api.trackforge.studio)

Check a catalogue against The MLC, look up a song's writers, publishers and ISWC, validate CWR files

- Trust score: 86/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.trackforge.studio`: 86/100 (this document), [markdown](https://verifymcp.io/servers/studio-trackforge-music-registration-check/api-v1-mcp.md), [page](https://verifymcp.io/servers/studio-trackforge-music-registration-check/api-v1-mcp)

## Channel facts

- Endpoint: `https://api.trackforge.studio/api/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http studio-trackforge-music-registration-check 'https://api.trackforge.studio/api/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "studio-trackforge-music-registration-check": {
      "url": "https://api.trackforge.studio/api/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "studio-trackforge-music-registration-check": {
      "type": "http",
      "url": "https://api.trackforge.studio/api/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.studio-trackforge-music-registration-check]
url = "https://api.trackforge.studio/api/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "studio-trackforge-music-registration-check": {
      "type": "remote",
      "url": "https://api.trackforge.studio/api/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add studio-trackforge-music-registration-check --url 'https://api.trackforge.studio/api/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  studio-trackforge-music-registration-check:
    url: "https://api.trackforge.studio/api/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "studio-trackforge-music-registration-check": {
      "Transport": "http",
      "Url": "https://api.trackforge.studio/api/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add studio-trackforge-music-registration-check -t streamable-http -u 'https://api.trackforge.studio/api/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "studio-trackforge-music-registration-check": {
      "type": "http",
      "url": "https://api.trackforge.studio/api/v1/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 86, +1)

- [security] Stability: 0.97 → pass

### 2026-11-03 (score 85, +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.

### 2026-11-01 (score 84, +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.

### 2026-10-30 (score 83, +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.

### 2026-10-28 (score 82, +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.

### 2026-10-26 (score 81, +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.

### 2026-10-23 (score 80, +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.

### 2026-10-21 (score 79, +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.

## MCP tools (4)

### `lookup_recording` (~438 tokens)

Song registration check: MLC registration, unclaimed shares, writers, publishers and ISWCs

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.

Input parameters:

- `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.

Output parameters:

- `ambiguous` (boolean)
- `candidates` (array)
- `input_kind`
- `mlc_source`
- `notes` (array)
- `query`
- `results` (array)

### `check_catalogue` (~205 tokens)

Catalogue registration check: up to 50 recordings against The MLC

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.

Input parameters:

- `isrcs` (array, required): ISRCs, 12 characters, e.g. USIR20400274 (hyphens and spaces allowed). At most 50; split larger catalogues into several calls.

Output parameters:

- `items` (array)
- `mlc_source`
- `summary`

### `validate_cwr` (~211 tokens)

CWR validation (CWR 2.1 file check)

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.

Input parameters:

- `cwr_text` (string, required): 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.

Output parameters:

- `error_count` (integer)
- `full_report` (string)
- `is_valid` (boolean)
- `issues` (array)
- `issues_total` (integer)
- `issues_truncated` (boolean)
- `line_endings_converted` (boolean)
- `recipient_profile` (string)
- `recipient_resolution` (object)
- `record_count` (integer)
- `spec_version` (string)
- `status_dimensions`
- `stored` (boolean)
- `transaction_count` (integer)
- `warning_count` (integer)

### `request_full_report` (~212 tokens)

Request a music royalties review (a person follows up)

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.

Input parameters:

- `catalogue_description` (string): Free-text description of the catalogue, e.g. artist names, number of songs, territories.
- `consent_to_contact` (boolean, required): True only if the user has agreed that TrackForge may contact them by email about this request.
- `email` (string, required): Contact email address for the follow-up.
- `isrcs` (array): ISRCs in the catalogue (up to 200). Give isrcs, catalogue_description, or both.
- `name` (string, required): Contact name.
- `organisation` (string): Optional label, publisher or company name.

Output parameters:

- `follow_up` (string)
- `isrcs_not_recognised` (array)
- `isrcs_recorded` (integer)
- `recorded` (boolean)
- `reference` (string)
- `report_generated` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/studio-trackforge-music-registration-check/api-v1-mcp#diagnostics

## Score history

- 2026-11-05: 86
- 2026-11-04: 85
- 2026-11-03: 85
- 2026-11-02: 84
- 2026-11-01: 84
- 2026-10-31: 83
- 2026-10-30: 83
- 2026-10-29: 82
- 2026-10-28: 82
- 2026-10-27: 81
- 2026-10-26: 81
- 2026-10-25: 80
- 2026-10-24: 80
- 2026-10-23: 80
- 2026-10-22: 79
- 2026-10-21: 79
- 2026-10-20: 78
- 2026-10-19: 78
- 2026-10-18: 77
- 2026-10-17: 77
- 2026-10-16: 76
- 2026-10-15: 76
- 2026-10-14: 75
- 2026-10-13: 75
- 2026-10-12: 74
- 2026-10-10: 73
- 2026-10-06: 72

## Common questions

### 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.

### What did VerifyMCP test on the TrackForge MCP server?

VerifyMCP ran 13 checks on TrackForge, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.trackforge.studio/api/v1/mcp
- Website: https://trackforge.studio/mcp
- Changelog RSS feed: https://verifymcp.io/servers/studio-trackforge-music-registration-check/api-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/studio-trackforge-music-registration-check/api-v1-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/studio-trackforge-music-registration-check/api-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/studio-trackforge-music-registration-check/api-v1-mcp