io.github.jmedure/talkback
NPM · TALKBACK-MCP · SCANNED SEP 24
Chat with your Ableton session in real-time.
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 Security98
- 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
- 39 of 125 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: the license (PolyForm-Shield-1.0.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 183 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 739 tokens (~73/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 47% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
How do I install the io.github.jmedure/talkback MCP server?
io.github.jmedure/talkback runs locally as an npm package, launched with npx -y talkback-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 · talkback-mcp
claude mcp add jmedure-talkback -- npx -y talkback-mcp
{
"mcpServers": {
"jmedure-talkback": {
"command": "npx",
"args": [
"-y",
"talkback-mcp"
]
}
}
} {
"servers": {
"jmedure-talkback": {
"command": "npx",
"args": [
"-y",
"talkback-mcp"
]
}
}
} codex mcp add jmedure-talkback -- npx -y talkback-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jmedure-talkback": {
"type": "local",
"command": [
"npx",
"-y",
"talkback-mcp"
],
"enabled": true
}
}
} openclaw mcp add jmedure-talkback --command npx --arg -y --arg talkback-mcp
mcp_servers:
jmedure-talkback:
command: "npx"
args: ["-y", "talkback-mcp"] {
"McpServers": {
"jmedure-talkback": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"talkback-mcp"
]
}
}
} assistant mcp add jmedure-talkback -t stdio -c npx -a -y talkback-mcp
{
"mcpServers": {
"jmedure-talkback": {
"command": "npx",
"args": [
"-y",
"talkback-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.
- 24 Sept 26 −3
- Stability: pass → 0.80 functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +2
- CVE-2026-82562 no longer affects this package ▲ security
- CVE-2026-82417 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 24 Sept 2026 · Analysed npm/talkback-mcp@0.1.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 125 packages
| Packages resolved | 125 |
|---|---|
| Stale | 39 |
| 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_mix ~95
Runs rule-based heuristic analysis for potential mix issues: frequency buildup, dynamics problems, routing inefficiencies, headroom. Only call when the user explicitly asks for mix feedback or describes a specific problem — do NOT call proactively. Findings are suggestions to consider, not problems to fix. Mix quality is subjective — frame results in context of what the user is trying to achieve. A technically 'imperfect' setting may be an intentional artistic choice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_group_track ~53
Creates a new group track containing the specified tracks. Always confirm with the producer first.
| Name | Type | Req | Description |
|---|---|---|---|
| group_name | string | yes | Name for the new group track |
| track_names | array | yes | Names of tracks to group |
No output schema declared.
No examples provided.
get_bridge_health ~54
Returns performance metrics from the M4L bridge device: poll execution time (avg/max), WebSocket message size, LiveAPI cache size, and track count. Use to diagnose performance issues or confirm the device is running efficiently.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_plugin_library ~50
Returns all audio plugins (AU, VST3) installed on this system. Use to know what tools the producer has available.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Optional search string to filter by plugin name |
No output schema declared.
No examples provided.
get_session_context ~72
Returns a snapshot of the current Ableton session: all tracks (names, volumes, panning, mutes, sends, device chains), return tracks, master track, and routing. Call once at the start of a conversation to orient yourself. No need to call again unless the user says the session has changed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_spectral_snapshot ~136
Captures ~2 seconds of live audio from the master bus and returns peak/RMS levels across frequency bands. Transport MUST be playing — coordinate with the user on which section to analyze (e.g., 'play the chorus'). This is a point-in-time microscope, not a full-song analyzer. Use as a secondary check to verify what device parameter analysis suggests, or to detect issues invisible in the device chain (masking, phase, resonances). For most frequency questions, reading EQ and filter parameters via get_track_details is more informative.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | – | 'master' for master bus, or a track name |
No output schema declared.
No examples provided.
get_track_details ~47
Returns full detail for a specific track including all devices, every parameter in human-readable units, and per-device observations.
| Name | Type | Req | Description |
|---|---|---|---|
| track_name | string | yes | Track name (case-insensitive match) |
No output schema declared.
No examples provided.
set_device_parameter ~117
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. Present the planned change with current → proposed values first, wait for a clear 'yes', then execute. If the user modifies the plan, re-present and re-confirm before executing.
| Name | Type | Req | Description |
|---|---|---|---|
| device_name | string | yes | – |
| parameter_name | string | yes | – |
| track_name | string | yes | – |
| unit | string | yes | – |
| value | number | yes | – |
No output schema declared.
No examples provided.
set_track_routing ~48
Changes a track's output routing. Always confirm with the producer first.
| Name | Type | Req | Description |
|---|---|---|---|
| output_target | string | yes | Name of the target track/group/bus |
| track_name | string | yes | – |
No output schema declared.
No examples provided.
toggle_device_bypass ~67
Enables or bypasses a device on a track. Useful for A/B comparison. Always confirm with the user before toggling.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | yes | true = device on, false = bypassed |
| device_name | string | yes | – |
| track_name | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.jmedure/talkback MCP server?
io.github.jmedure/talkback is an MCP server listed in the public MCP registry as io.github.jmedure/talkback. Chat with your Ableton session in real-time. This page covers its npm package (talkback-mcp).
Is the io.github.jmedure/talkback MCP server safe to use?
io.github.jmedure/talkback scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 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 io.github.jmedure/talkback MCP server expose?
io.github.jmedure/talkback exposes 10 tools: get_session_context, get_track_details, get_spectral_snapshot, get_plugin_library, analyze_mix, and 5 more. Their descriptions and schemas cost roughly 739 tokens of context every time the server is loaded.
Is the io.github.jmedure/talkback MCP server still maintained?
io.github.jmedure/talkback is still listed as active in the MCP registry. We last reached this channel on 24 September 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 io.github.jmedure/talkback MCP server under?
io.github.jmedure/talkback declares the PolyForm-Shield-1.0.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.