# Tag-per-Track (npm · tag-per-track-mcp) Audio analysis and A&R scoring for music tracks: tags, lyrics, artist stats, demo triage. - Trust score: 70/100 (medium) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-10-06 ## Components - npm · `tag-per-track-mcp`: 70/100 (this document), [markdown](https://verifymcp.io/servers/lory97-tag-per-track-mcp/tag-per-track-mcp.md), [page](https://verifymcp.io/servers/lory97-tag-per-track-mcp/tag-per-track-mcp) ## Channel facts - Registry: `npm` - Package: `tag-per-track-mcp` - Version: `1.6.3` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-10-06. - **Supply Chain Security**: 99/100 - No malware found by supply-chain analysis. - No known CVEs affecting this package version or its production dependencies. - No install/post-install scripts declared. - 33 of 120 dependencies flagged as unhealthy. - **Provenance & Transparency**: 45/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (MIT). - Actively maintained (last published 5 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 75/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (excellent). - 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. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 0/100 - Stability not yet verified: not enough scan history yet (needs a 30-day window). - **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. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 5 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. **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. ## Install ### 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. ### Claude ```bash claude mcp add lory97-tag-per-track-mcp -- npx -y tag-per-track-mcp ``` ### Cursor ```json { "mcpServers": { "lory97-tag-per-track-mcp": { "command": "npx", "args": [ "-y", "tag-per-track-mcp" ] } } } ``` ### VS Code ```json { "servers": { "lory97-tag-per-track-mcp": { "command": "npx", "args": [ "-y", "tag-per-track-mcp" ] } } } ``` ### Codex ```bash codex mcp add lory97-tag-per-track-mcp -- npx -y tag-per-track-mcp ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "lory97-tag-per-track-mcp": { "type": "local", "command": [ "npx", "-y", "tag-per-track-mcp" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add lory97-tag-per-track-mcp --command npx --arg -y --arg tag-per-track-mcp ``` ### Hermes ```yaml mcp_servers: lory97-tag-per-track-mcp: command: "npx" args: ["-y", "tag-per-track-mcp"] ``` ### Netclaw ```json { "McpServers": { "lory97-tag-per-track-mcp": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "tag-per-track-mcp" ] } } } ``` ### Vellum ```bash assistant mcp add lory97-tag-per-track-mcp -t stdio -c npx -a -y tag-per-track-mcp ``` ### Other ```json { "mcpServers": { "lory97-tag-per-track-mcp": { "command": "npx", "args": [ "-y", "tag-per-track-mcp" ] } } } ``` ## 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-10-02 (score 70, +15) - [security improvement] Malware scan: unverified → pass ### 2026-10-01 (score 55) First indexed and scored. ## MCP tools (5) ### `analyze_audio` (~328 tokens) 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). Input parameters: - `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. ### `analyze_audio_with_lyrics` (~193 tokens) 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). Input parameters: - `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. ### `triage_demo_folder` (~525 tokens) 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. Input parameters: - `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, required): 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. ### `analyze_audio_batch` (~300 tokens) 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). Input parameters: - `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'. ### `lookup_artist_stats` (~93 tokens) Retrieves streaming traction and commercial metrics for an artist (Spotify monthly listeners, followers, popularity score) for A&R qualification. Input parameters: - `artist_name` (string, required): 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. ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/lory97-tag-per-track-mcp/tag-per-track-mcp#diagnostics ## Score history - 2026-10-06: 70 - 2026-10-05: 70 - 2026-10-04: 70 - 2026-10-03: 70 - 2026-10-02: 70 - 2026-10-01: 55 ## Common questions ### 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. ## Links - npm package: https://www.npmjs.com/package/tag-per-track-mcp - Socket report: https://socket.dev/npm/package/tag-per-track-mcp - Repository: https://github.com/Lory97/tag-per-track-mcp - Website: https://tag-per-track.cloud/ - Changelog RSS feed: https://verifymcp.io/servers/lory97-tag-per-track-mcp/tag-per-track-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/lory97-tag-per-track-mcp/tag-per-track-mcp.json - HTML version of this page: https://verifymcp.io/servers/lory97-tag-per-track-mcp/tag-per-track-mcp