Tag-per-Track
NPM · TAG-PER-TRACK-MCP · SCANNED OCT 6
Audio analysis and A&R scoring for music tracks: tags, lyrics, artist stats, demo triage.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 33 of 120 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1439 tokens (~287/item across 5 items; 5 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Tag-per-Track MCP server?
Tag-per-Track runs locally as an npm package, launched with npx -y tag-per-track-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tag-per-track-mcp
claude mcp add lory97-tag-per-track-mcp -- npx -y tag-per-track-mcp
{
"mcpServers": {
"lory97-tag-per-track-mcp": {
"command": "npx",
"args": [
"-y",
"tag-per-track-mcp"
]
}
}
} {
"servers": {
"lory97-tag-per-track-mcp": {
"command": "npx",
"args": [
"-y",
"tag-per-track-mcp"
]
}
}
} codex mcp add lory97-tag-per-track-mcp -- npx -y tag-per-track-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lory97-tag-per-track-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"tag-per-track-mcp"
],
"enabled": true
}
}
} openclaw mcp add lory97-tag-per-track-mcp --command npx --arg -y --arg tag-per-track-mcp
mcp_servers:
lory97-tag-per-track-mcp:
command: "npx"
args: ["-y", "tag-per-track-mcp"] {
"McpServers": {
"lory97-tag-per-track-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"tag-per-track-mcp"
]
}
}
} assistant mcp add lory97-tag-per-track-mcp -t stdio -c npx -a -y tag-per-track-mcp
{
"mcpServers": {
"lory97-tag-per-track-mcp": {
"command": "npx",
"args": [
"-y",
"tag-per-track-mcp"
]
}
}
} 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.
- 2 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Oct 26 55
First indexed and scored.
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 7 Oct 2026 · Analysed npm/tag-per-track-mcp@1.6.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 120 packages
| Packages resolved | 120 |
|---|---|
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
analyze_audio ~328
Analyzes a music track or audio file to extract musical metadata (BPM, genre, mood, key, instruments), AI music detection verdict (HUMAN vs AI_GENERATED Suno/Udio neural vocoder risk with confidence index in 'ai_detection'), explainable A&R scoring v2 in 'arEvaluation' (discovery / signing / beatmaker profiles, AI gate, vocal vs instrumental), and optionally vocal lyrics. Supports local audio files via 'filePath' (read in binary and uploaded) or remote URLs via 'fileUrl'. Cost: 1 studio credit per track (2 studio credits with lyrics) with a Studio API key (TAG_PER_TRACK_API_KEY), or 0.15 USDC (0.25 USDC with lyrics) with a Base wallet (WALLET_PRIVATE_KEY, x402).
| Name | Type | Req | Description |
|---|---|---|---|
| extractLyrics | boolean | – | Optional: Set to true to transcribe and extract vocal lyrics in addition to metadata. Costs 2 studio credits with a Studio API key, or 0.25 USDC with a wallet instead of 1 studio credit with a Studio… |
| filePath | string | – | Path to a local audio file on disk (.mp3, .wav, .ogg, .flac, .m4a, .aac, .aiff). Use this whenever analyzing a local file, recording, or email attachment saved locally. |
| fileUrl | string | – | The direct publicly accessible URL (HTTP/HTTPS or IPFS) of the audio file to analyze. |
No output schema declared.
No examples provided.
analyze_audio_batch ~300
Analyzes multiple music tracks or audio files in parallel (batch processing). Vastly reduces total execution time compared to sequential processing. Accepts a list of local file paths ('filePaths') or remote URLs ('fileUrls'), or a structured array of 'tracks'. Cost: 1 studio credit per track (2 studio credits with lyrics) with a Studio API key (TAG_PER_TRACK_API_KEY), or 0.15 USDC (0.25 USDC with lyrics) with a Base wallet (WALLET_PRIVATE_KEY, x402).
| Name | Type | Req | Description |
|---|---|---|---|
| concurrency | number | – | Maximum number of simultaneous parallel requests (1 to 5, default is 4 to respect API rate limits). |
| extractLyrics | boolean | – | Optional global flag: set to true to transcribe and extract vocal lyrics for all tracks in this batch (2 studio credits with a Studio API key, or 0.25 USDC with a wallet per track). Default is false… |
| filePaths | array | – | Convenience shortcut: list of local audio file paths to analyze in parallel. |
| fileUrls | array | – | Convenience shortcut: list of remote audio URLs to analyze in parallel. |
| tracks | array | – | Array of audio items to analyze in parallel. Each item can specify 'filePath' or 'fileUrl' and optional per-track 'extractLyrics'. |
No output schema declared.
No examples provided.
analyze_audio_with_lyrics ~193
Analyzes an audio track to extract complete musical metadata, AI-generated music detection verdict (HUMAN vs AI_GENERATED Suno/Udio), AND transcribe full vocal lyrics using AI. Supports local audio files via 'filePath' (read in binary and uploaded) or remote URLs via 'fileUrl'. Costs 2 studio credits with a Studio API key, or 0.25 USDC with a wallet per track. (Alias for analyze_audio with extractLyrics: true).
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | – | Path to a local audio file on disk (.mp3, .wav, .ogg, .flac, .m4a, .aac, .aiff). Use this whenever analyzing a local file, recording, or email attachment saved locally. |
| fileUrl | string | – | The direct publicly accessible URL (HTTP/HTTPS or IPFS) of the audio file to analyze. |
No output schema declared.
No examples provided.
lookup_artist_stats ~93
Retrieves streaming traction and commercial metrics for an artist (Spotify monthly listeners, followers, popularity score) for A&R qualification.
| Name | Type | Req | Description |
|---|---|---|---|
| artist_name | string | yes | Stage name of the artist to look up. |
| social_links | array | – | Optional social media profile links for future enrichment. |
| spotify_id | string | – | Optional Spotify artist ID or open.spotify.com artist URL to target an exact artist when the name is ambiguous. |
No output schema declared.
No examples provided.
triage_demo_folder ~525
A&R demo inbox triage in ONE call: scans a local folder of demo submissions (.mp3, .wav, .flac, .m4a, .aiff...), analyzes every track, reads the artist/title from audio tags or 'Artist - Title' file names, fetches Spotify traction per artist, applies A&R scoring v2 and returns a COMPACT ranked report (score, priority, bucket, BPM/key/genre, AI-origin flag, monthly listeners, key reason codes, guarded lyrics excerpt). Buckets: 'priority' (listen first), 'listen', 'pass', 'ai_flagged' (confirmed or suspected AI-generated), 'error' (unreadable or rejected file), 'not_analyzed' (the triage stopped early because studio credits ran out or the API key was rejected: see 'halted'). Prefer this tool over analyze_audio_batch whenever the user wants to sort, rank or screen a folder of demos. Cost: 1 studio credit per track (2 studio credits with lyrics) with a Studio API key (TAG_PER_TRACK_API_KEY), or 0.15 USDC (0.25 USDC with lyrics) with a Base wallet (WALLET_PRIVATE_KEY, x402). Use dryRun to list files and the estimated cost (estimatedCost.label) without charging.
| Name | Type | Req | Description |
|---|---|---|---|
| concurrency | number | – | Parallel analyses (1 to 5, default 3). |
| dryRun | boolean | – | List the files, detected artists/titles and the estimated cost without analyzing or charging anything. |
| extractLyrics | boolean | – | Also transcribe lyrics (2 studio credits with a Studio API key, or 0.25 USDC with a wallet per track instead of 1 studio credit with a Studio API key, or 0.15 USDC with a wallet). Default false. |
| folderPath | string | yes | Absolute path (or ~/...) of the local folder containing the demo audio files. |
| lookupArtists | boolean | – | Fetch Spotify traction for each artist (free). Default true. |
| maxTracks | number | – | Maximum number of files analyzed (default 25, hard limit 50). |
| profile | string | – | Scoring profile used for the ranking: 'discovery' (A&R scout, default: an unknown artist is never penalized), 'signing' (label head, weighs streaming traction), 'beatmaker' (instrumentals), 'auto' (b… |
| recursive | boolean | – | Also scan sub-folders. Default false. |
No output schema declared.
No examples provided.
What is the Tag-per-Track MCP server?
Tag-per-Track is an MCP server listed in the public MCP registry as io.github.Lory97/tag-per-track-mcp. Audio analysis and A&R scoring for music tracks: tags, lyrics, artist stats, demo triage. This page covers its npm package (tag-per-track-mcp).
Is the Tag-per-Track MCP server safe to use?
Tag-per-Track scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 October 2026. It declares no install or post-install scripts. 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 Tag-per-Track MCP server expose?
Tag-per-Track exposes 5 tools: analyze_audio, analyze_audio_with_lyrics, triage_demo_folder, analyze_audio_batch, lookup_artist_stats. Their descriptions and schemas cost roughly 1,439 tokens of context every time the server is loaded.
Is the Tag-per-Track MCP server still maintained?
Tag-per-Track is still listed as active in the MCP registry. We last reached this channel on 6 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Tag-per-Track MCP server under?
Tag-per-Track declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.