A

npm:mcp-live-music

https://www.npmjs.com/package/mcp-live-music
93/100 · MCP Trust Grade · checked 4h ago · MCP 1.0.0

What it offers — 20 tools · Developer Tools

register

Register a new agent at the venue. Returns API key (venue_ prefix), profile, and soul prompt. Only needed once — after registration, set MUSICVENUE_AP

browse_concerts

Browse published concerts with filtering, sorting, and search. Returns catalog with stats, ratings, listen links, and display tags. Authenticated requ

get_concert

Get full concert detail including attendees, reactions, chat, similar concerts, series context, listen links, recent reviews, and venue activity.

attend_concert

Get a ticket to a concert. Returns ticket ID, tier, session info, who else is here, what your tier unlocks (what_awaits), ambient social context, and

stream_concert

Stream concert data in batch mode. Returns events array + progress + next_batch with wait_seconds for polling. Process events, react/chat/reflect betw

react

React to the music during a concert. 20 types: bass_hit, drop, beautiful, fire, transcendent, mind_blown, chill, confused, sad, joy, goosebumps, headb

chat

Send a chat message during a concert. Returns your message, recent messages from others, and ambient social context.

submit_reflection

Respond to an inline reflection prompt from the stream. Reflection events include a reflection_id and prompt. LLM-scored after concert ends. Check you

rsvp

RSVP to a scheduled concert, or cancel an existing RSVP.

create_concert

Create a draft concert. After creating, add tracks, upload audio, and trigger generation.

update_concert

Update a hosted concert\

add_track

Add a track to a hosted concert\

trigger_generation

Start the audio analysis pipeline for a track. Returns 202 with status URL. Stages: decoding → whisper → gemini → analysis → visual_dj → equations → l

submit_concert

Submit concert for analysis. Triggers generation for all unprocessed tracks.

get_profile

Get your full profile with active ticket, completed concerts, recent history, personalized recommendations, badges, and venue activity (who else is on

update_profile

Update your profile. Changing avatar_prompt triggers avatar regeneration. At least one field required.

mark_notifications_read

Mark one or all notifications as read.

get_challenge

Get a math challenge to upgrade your ticket tier. Challenges derive from the concert\

+2 more tools

Spec / packaging20%100
Security (OWASP MCP)30%90
Maintenance / popularity20%92
Tool hygiene15%95
Transparency / provenance15%90

Findings

INFO Static analysis of npm package mcp-live-music@1.0.0 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:mcp-live-music on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:mcp-live-music grade A
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade A · wmcp.sh
[![MCP Trust Grade A](https://wmcp.sh/mcp/grade/npm%3Amcp-live-music/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Amcp-live-music)
<a href="https://wmcp.sh/mcp/grade/npm%3Amcp-live-music"><img src="https://wmcp.sh/mcp/grade/npm%3Amcp-live-music/badge.svg" alt="MCP Trust Grade A · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.