Keyboards MCP Server
keyboards-mcp
npm
v2.1.0
Source verified
Published by uribrecher — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP server for controlling MIDI keyboards (Nord Electro 5D and more)
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 4
medium Dynamic module load from a non-literal (dist/shared/device-pool.js)MTC-SRC-005
In the server's implementation (`dist/shared/device-pool.js:35`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: -friendly error. */ require(index) { const entry = this.devices.get(index); if (!entry) {
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/shared/device-pool.js
medium Dynamic module load from a non-literal (dist/shared/model-registry.js)MTC-SRC-005
In the server's implementation (`dist/shared/model-registry.js:33`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const mod = await import(indexPath); const model = mod.default; models.push(model.
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/shared/model-registry.js
medium Dynamic module load from a non-literal (dist/tools/extract-backup.js)MTC-SRC-005
In the server's implementation (`dist/tools/extract-backup.js:64`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: model = pool.require(device).device.model; } catch (err) { return {
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/tools/extract-backup.js
low Shell/command execution in packaging/dev tooling (dist/cli/install.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`dist/cli/install.js:4`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { execFile } from "node:child_process"; import { promisify } from "node:util"; import { getMcbHealth } from "../shared/m
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/cli/install.js
Tools 16
Each tool and what it can reach — statically extracted from the published source.
web_searchingests untrusted inputconnect_to_keyboardno sensitive capabilitydisconnect_from_keyboardno sensitive capabilityextract_backupno sensitive capabilityget_current_stateno sensitive capabilityget_healthno sensitive capabilityget_last_backup_locationno sensitive capabilityget_system_promptno sensitive capabilityis_connectedno sensitive capabilitylist_midi_devicesno sensitive capability
Show 6 more tools ↓
list_parametersno sensitive capabilitylist_programsno sensitive capabilitylist_songsno sensitive capabilityload_programno sensitive capabilityload_songno sensitive capabilityset_parametersno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (16 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.1.0 latest |
A 97/100 | 4 | 1.13.0 | 2026-09-08 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan keyboards-mcp --onlineMore in Other
A Model Context Protocol server implementation for AdGuard Home that enables AI agents to query and manage DNS records, filtering rules and more
Identity oracle and trust layer for autonomous AI agents. Bidirectional KYA and trust scoring.
MCP server with Airtable integration
A free one-minute reset for people, delivered by AI, with no account or personal data.
Access SEC filings efficiently, save time and tokens, and get cited answers.
A smart [MCP](https://modelcontextprotocol.io) server for [AniList](https://anilist.co) that gets your anime/manga taste - not just API calls.