Elektron MCP Server

elektron-mcp PyPI v0.2.4

Published by zerubeus — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MPC to control Elektron machines (Digitakt 2, Digitone 2)

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

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 − 1 = 99. 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:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 64

Each tool and what it can reach — statically extracted from the published source.

  • set_amp_attackno sensitive capability
  • set_amp_decayno sensitive capability
  • set_amp_envelope_modeno sensitive capability
  • set_amp_envelope_resetno sensitive capability
  • set_amp_holdno sensitive capability
  • set_amp_panno sensitive capability
  • set_amp_releaseno sensitive capability
  • set_amp_sustainno sensitive capability
  • set_amp_volumeno sensitive capability
  • set_fx_bit_reductionno sensitive capability
Show 54 more tools ↓
  • set_fx_chorusno sensitive capability
  • set_fx_delayno sensitive capability
  • set_fx_overdriveno sensitive capability
  • set_fx_overdrive_routingno sensitive capability
  • set_fx_reverbno sensitive capability
  • set_fx_sample_rate_reductionno sensitive capability
  • set_fx_sample_rate_routingno sensitive capability
  • set_lfo1_depthno sensitive capability
  • set_lfo1_destinationno sensitive capability
  • set_lfo1_fadeno sensitive capability
  • set_lfo1_multiplierno sensitive capability
  • set_lfo1_speedno sensitive capability
  • set_lfo1_start_phaseno sensitive capability
  • set_lfo1_trigger_modeno sensitive capability
  • set_lfo1_waveformno sensitive capability
  • set_lfo2_depthno sensitive capability
  • set_lfo2_destinationno sensitive capability
  • set_lfo2_fadeno sensitive capability
  • set_lfo2_multiplierno sensitive capability
  • set_lfo2_speedno sensitive capability
  • set_lfo2_start_phaseno sensitive capability
  • set_lfo2_trigger_modeno sensitive capability
  • set_lfo2_waveformno sensitive capability
  • set_multimode_filter_attackno sensitive capability
  • set_multimode_filter_decayno sensitive capability
  • set_multimode_filter_envelope_depthno sensitive capability
  • set_multimode_filter_frequencyno sensitive capability
  • set_multimode_filter_releaseno sensitive capability
  • set_multimode_filter_resonanceno sensitive capability
  • set_multimode_filter_sustainno sensitive capability
  • set_multimode_filter_typeno sensitive capability
  • set_wavetone_attackno sensitive capability
  • set_wavetone_decayno sensitive capability
  • set_wavetone_driftno sensitive capability
  • set_wavetone_holdno sensitive capability
  • set_wavetone_mod_typeno sensitive capability
  • set_wavetone_noise_baseno sensitive capability
  • set_wavetone_noise_characterno sensitive capability
  • set_wavetone_noise_levelno sensitive capability
  • set_wavetone_noise_typeno sensitive capability
  • set_wavetone_noise_widthno sensitive capability
  • set_wavetone_osc1_levelno sensitive capability
  • set_wavetone_osc1_offsetno sensitive capability
  • set_wavetone_osc1_phase_distortionno sensitive capability
  • set_wavetone_osc1_pitchno sensitive capability
  • set_wavetone_osc1_waveformno sensitive capability
  • set_wavetone_osc1_wavetableno sensitive capability
  • set_wavetone_osc2_levelno sensitive capability
  • set_wavetone_osc2_offsetno sensitive capability
  • set_wavetone_osc2_phase_distortionno sensitive capability
  • set_wavetone_osc2_pitchno sensitive capability
  • set_wavetone_osc2_waveformno sensitive capability
  • set_wavetone_osc2_wavetableno sensitive capability
  • set_wavetone_reset_modeno sensitive capability

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v0.2.4 latest A 99/100 0 1.13.0 2026-08-25

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.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/elektron-mcp/badge.svg)](https://mcptrustchecker.com/registry/elektron-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/elektron-mcp"><img src="https://mcptrustchecker.com/registry/elektron-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/elektron-mcp/badge.json via https://img.shields.io/endpoint?url=…

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 elektron-mcp --online --registry pypi

Use the free API → How scoring works

More in Design & Media