F

npm:talkback-mcp

https://www.npmjs.com/package/talkback-mcp
55/100 · MCP Trust Grade · checked 4h ago · MCP 0.1.13

What it offers — 10 tools · Developer Tools

get_session_context

Returns a snapshot of the current Ableton session: all tracks (names, volumes, panning, mutes, sends, device chains), return tracks, master track, and

get_track_details

Returns full detail for a specific track including all devices, every parameter in human-readable units, and per-device observations.

get_spectral_snapshot

Captures ~2 seconds of live audio from the master bus and returns peak/RMS levels across frequency bands. Transport MUST be playing — coordinate with

get_plugin_library

Returns all audio plugins (AU, VST3) installed on this system. Use to know what tools the producer has available.

analyze_mix

Runs rule-based heuristic analysis for potential mix issues: frequency buildup, dynamics problems, routing inefficiencies, headroom. Only call when th

set_device_parameter

Sets a device parameter to a new value. Pass values in human-readable units (dB, ms, Hz, ratio, percent). NEVER call without explicit user approval. P

toggle_device_bypass

Enables or bypasses a device on a track. Useful for A/B comparison. Always confirm with the user before toggling.

create_group_track

Creates a new group track containing the specified tracks. Always confirm with the producer first.

set_track_routing

Changes a track

get_bridge_health

Returns performance metrics from the M4L bridge device: poll execution time (avg/max), WebSocket message size, LiveAPI cache size, and track count. Us

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

Findings

FAILMCP01 Prompt-injection / hidden-instruction markup found in package source.
INFO Static analysis of npm package talkback-mcp@0.1.13 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:talkback-mcp 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:talkback-mcp grade F
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 F · wmcp.sh
[![MCP Trust Grade F](https://wmcp.sh/mcp/grade/npm%3Atalkback-mcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Atalkback-mcp)
<a href="https://wmcp.sh/mcp/grade/npm%3Atalkback-mcp"><img src="https://wmcp.sh/mcp/grade/npm%3Atalkback-mcp/badge.svg" alt="MCP Trust Grade F · 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.