Mmcp.market

Tag-per-Track MCP server

by Lory97·io.github.Lory97/tag-per-track-mcp·v1.6.3

Audio analysis and A&R scoring for music tracks: tags, lyrics, artist stats, demo triage.

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

0 stars887 downloads/wk

Reviews

Write one

Nobody has reviewed Tag-per-Track yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Tag-per-Track tools (5)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • analyze_audio

    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 file

  • analyze_audio_batch

    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'. …

  • analyze_audio_with_lyrics

    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 … per track. (Alias for analyze_audio with extractLyrics: true).

  • lookup_artist_stats

    Retrieves streaming traction and commercial metrics for an artist (Spotify monthly listeners, followers, popularity score) for A&R qualification.

  • triage_demo_folder

    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, guar

Public scan report

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

no findings
  • Code scan9 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install Tag-per-Track in Claude Code, Cursor or VS Code

Runs npx -y tag-per-track-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add tag-per-track-mcp -- npx -y tag-per-track-mcp
Add to Cursor

What the publisher says

From the Tag-per-Track repository's README, as published. We do not edit it. Read it on GitHub

Tag-per-Track MCP Server

This project is a local Model Context Protocol (MCP) server that allows AI agents (like Claude) to analyze audio files via the Tag-per-Track API. It authenticates either with a Studio API key (prepaid credits bought on tag-per-track.cloud, no crypto needed) or with a wallet, in which case it automatically handles the USDC micro-payment using the x402 protocol on the Base network.

🎯 Vision

Enable an AI to "pay to listen" autonomously. When an AI agent wants to analyze a track, it uses this MCP server, which signs an EIP-3009 (USDC) payment authorization and instantly retrieves the enriched track metadata.

🚀 Features

  • analyzeaudio Tool (Canonical): Extracts BPM, Genre, Mood, Key, Instruments, production metrics, optional Lyrics (1 credit or 0.15 USDC standard / 2 credits or 0.25 USDC with lyrics), AI-Generated Music Detection (aidetection: Suno, Udio, neural vocoders with HUMAN, AIGENERATED, or UNCERTAIN verdicts) and the server-side A&R evaluation** (arEvaluation: discovery / signing / beatmaker profiles).
  • analyzeaudiowithlyrics Tool (Alias)**: Extracts complete musical metadata, transcribes full vocal lyrics, and returns AI origin integrity metrics (2 credits or 0.25 USDC).
  • analyzeaudiobatch Tool (Parallel Processing): Analyzes multiple music tracks concurrently with AI origin detection on every track, dramatically reducing turnaround time for albums and playlists.
  • triagedemofolder Tool (Demo Inbox Triage): Sorts a whole local folder of demos in one call: analysis, artist/title from Artist - Title file names or audio tags, Spotify traction, A&R scoring v2 re-computed with the traction, and a compact ranked report with buckets (priority, listen, pass, ai_flagged, error). Unreliable lyrics (instrumental, no voice, looping hallucination) are flagged instead of quoted.
  • lookupartiststats Tool (A&R Traction): Fetches public Spotify streaming traction (monthly listeners, followers, popularity score, genres) for hybrid A&R qualification.
  • Selective Audio Compression: Automatically compresses heavy uncompressed files (.wav, .aiff, .aif) or audio files larger than 15 MB to 128 kbps AAC (.m4a) before upload (using native macOS afconvert or ffmpeg), reducing upload bandwidth and latency by up to 90% while leaving lightweight files (.mp3, .m4a $\le 15$ MB) untouched.
  • Prices in the Right Unit: tool descriptions, prompts and reports state costs in studio credits when a Studio API key is configured, and in USDC only in wallet (x402) mode, so an A&R paying with credits never sees crypto amounts.
  • Dual Authentication: Studio API key (Authorization: Bearer tptlive…, prepaid credits) takes priority over the Web3 wallet.
  • Automated x402 Payment: Manages the x402 challenge-response cycle (HTTP 402), with the platform wallet and USDC contracts pinned client-side.
  • Integrated Web3: On-chain signing via viem (EIP-3009 TransferWithAuthorization on Base).
  • Client-Side Financial Guard (Spending Cap): Built-in spending limit (default 0.50 USDC max per call) protecting your wallet against abnormal requests.
  • Confidential by Default for x402: Wallet-paid analyses are sent with x-no-persist (not stored server-side); Studio API key analyses are saved to your dashboard history unless TAGPERTRACKNOPERSIST=1.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Tag-per-Track: common questions

Is Tag-per-Track MCP server safe?
Mostly: it is graded B (83/100). Read the Tag-per-Track safety report
How do I install Tag-per-Track?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Tag-per-Track need an API key?
Yes. The registry entry asks for TAG_PER_TRACK_API_KEY, WALLET_PRIVATE_KEY.
Is Tag-per-Track maintained?
The last commit was 6 days ago (2026-10-01). The latest release is v1.6.3.
What can I use instead of Tag-per-Track?
Servers from other publishers that do the same job: StemLab — timing and loops for Shorts MCP server, Aetherwave MCP server and ElevenLabs MCP server. Compare all Tag-per-Track alternatives.

Alternatives to Tag-per-Track

Same job from other publishers: the closest match first, then the best rated.

All Tag-per-Track alternatives →
  • StemLab — timing and loops for Shorts
    Audio timing and loopable section analysis for music, Shorts, and short-form video workflows.
    A
  • Aetherwave
    Music, image, video and audio generation across top AI providers - one key, one credit pool.
    B
  • ElevenLabs
    ElevenLabs MCP server: TTS, music, sound effects, voices, and audio transcription
    A
  • Jovie
    Create a music artist's Jovie profile from a Spotify URL and read public artist data.
    A
  • FunASR
    Transcribe local audio with FunASR and SenseVoice using private, on-device inference.
    A

More from Lory97 →