Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

stlink-mcp

PYPI · STLINK-MCP

Program, run and inspect STM32 targets over ST-LINK; every result verified, unverified or failed.

Available components

0 this week 73 Trust /100

Last scanned (18 hours ago)

Scores higher than 66% of PyPI servers

Category IoT and Hardware

Trust breakdown (7 categories)

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 Security93
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Declares code that runs automatically (build-time code we could not rule out (a Hatch, PDM or setuptools build hook, a dynamic version we could not read statically, shipped VCS metadata or a stray root module)) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • 2 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to dii/stlink-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 12 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2684 tokens (~167/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 13 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 11 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
Diagnostics

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 21 Nov 2026 · Analysed pypi/stlink-mcp@0.9.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo dii/stlink-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/dii/stlink-mcp/.github/workflows/publish.yml@refs/tags/v0.9.0
Rekor log index 3751552358
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:698aa9ab6b04b2caf9aaeb665560d6ae0a150a354c7b52955ce91c87552ea3fc

Background: How many MCP packages publish verified provenance →

Install scripts 2 scripts
Hook Tier Command
build_backend Known build tool hatchling.build
build_hook Not reviewed tool.hatch.version.source

Background: Why install scripts are a supply-chain risk →

Dependencies 30 packages
Packages resolved 30
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~2,282 tokens

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 →

Tool Tokens
board_state ~145

Identify the target, the probe and its family, and say whether the core is running, sleeping, halted or locked up, from program-counter samples read without halting it; given `elf_path`, where in the source they fall. If the core cannot be reached as it runs, reconnects through a reset, which restarts the program and can get past a debug port the program closed; `target_was_reset` says so. Never resets beside a GDB server holding the probe. `family.provenance` says which values were measured.

NameTypeReqDescription
elf_path–––
interfacestring––
probe_serial–––

Structured output declared, but exposes no named fields.

No examples provided.

capture_console ~126

Capture what a target prints on its serial console for up to 60 seconds. The port is the one the probe list maps to this probe's serial, or the one STLINK_MCP_CONSOLE names for it, never the first /dev/ttyACM*; refused when there is none. What the probe buffered before the port opened comes back separately, in `console_buffered`. Hearing nothing is unverified: silence cannot be told from a port not wired to the target.

NameTypeReqDescription
probe_serial–––
secondsnumber––

Structured output declared, but exposes no named fields.

No examples provided.

capture_swo ~146

Capture what the target writes to an ITM stimulus port, over the SWO pin. `core_clock_hz` is the clock the core runs at while it writes; a wrong one gives nothing or garbled text. Does not halt or reset, but turns trace output on and leaves it on, taking the SWO pin from the application until a power cycle. SWD only. Works beside a GDB server holding the probe when stlink-server is installed. Hearing nothing is unverified.

NameTypeReqDescription
core_clock_hzintegeryes–
itm_portinteger––
probe_serial–––
secondsnumber––

Structured output declared, but exposes no named fields.

No examples provided.

core_registers ~135

Read the core registers, halting the core for the read; with `elf_path`, also the call stack with each frame's arguments and locals. Says whether the core runs again afterwards. Works while run_until holds the core halted, and leaves it so. Without `elf_path`, a core it cannot reach as it runs is reached through a reset, which `target_was_reset` reports; with `elf_path` it refuses instead. Halts the core, so not for routine checks.

NameTypeReqDescription
elf_path–––
interfacestring––
probe_serial–––

Structured output declared, but exposes no named fields.

No examples provided.

disassemble ~139

Disassemble a function, or the code around an address, from the ELF, with each instruction's source file and line and the function an inlined copy comes from. `location` is a function name or an address. Without `probe_serial` it reads only the ELF; with it, it also compares the target's code with the ELF's, without halting, and is verified only when they match. At most 256 instructions; `cut` says when there were more.

NameTypeReqDescription
elf_pathstringyes–
interfacestring––
locationstringyes–
probe_serial–––

Structured output declared, but exposes no named fields.

No examples provided.

flash_firmware ~140

Program an image into flash: a raw .bin at `address` or at a measured flash base, or an ELF or HEX file at its own addresses, inside the part's flash; on a base from ST's database or a board file, only inside the main-flash window; the result names the base's provenance. Verified only when every byte reads back the same. Does not sign or start the image; `next_step` says how it boots. Prefer run_firmware while developing.

NameTypeReqDescription
address–––
image_pathstringyes–
interfacestring––
probe_serial–––

Structured output declared, but exposes no named fields.

No examples provided.

list_probes ~91

List every attached ST-LINK with its firmware, board name, serial console and whether a GDB server holds it. Use the console mapping rather than the order of /dev/ttyACM*, which does not follow the probes. Listing takes about a second, and often much longer while a GDB server holds a probe, which is why the other tools should be given `probe_serial`.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

locate_fault ~134

Find the instruction that faulted, from the exception frame. Halts the core to read registers, and never resets it, since a reset loses the fault: refuses when the core cannot be reached without one. Call it while the core sits in a fault handler. Returns the stacked PC and LR, from the stack that EXC_RETURN in LR names; with `elf_path`, their functions and source lines. Refuses when the core is not in a handler or LR no longer holds EXC_RETURN.

NameTypeReqDescription
elf_path–––
interfacestring––
probe_serial–––

Structured output declared, but exposes no named fields.

No examples provided.

read_fault_status ~129

Read and decode the Cortex-M fault status registers without halting or resetting the target. They stay set until software or a reset clears them, so call this first after a crash; a probe run_firmware still holds resets a core that locks up, which clears them. Says whether a fault is active, what happened in plain words, the faulting address when the hardware recorded it, and how to find the instruction. Refuses Cortex-M0, M0+, M1 and M23 cores.

NameTypeReqDescription
interfacestring––
probe_serial–––

Structured output declared, but exposes no named fields.

No examples provided.

read_memory ~195

Read target memory without halting or resetting it, given one of: `address` (an integer or a "0x..." string, 4-byte aligned, `length_bytes` a multiple of 4, at most 1024); `symbol`, a variable decoded with the types in `elf_path`; or `register`, such as "RCC.CR", decoded from ST's SVD file for the part (`svd` picks one). Refuses a register whose read changes state, such as a UART's data register, unless `read_effects_ok`. Refuses rather than reset at a closed debug port.

NameTypeReqDescription
address–––
elf_path–––
interfacestring––
length_bytesinteger––
probe_serial–––
read_effects_okboolean––
register–––
svd–––
symbol–––

Structured output declared, but exposes no named fields.

No examples provided.

read_option_bytes ~125

Read the option bytes as ST's programmer reads and explains them: readout protection first, then each section, such as brown-out level, user configuration, boot addresses and write protection, with every value and its meaning. Read only: no tool here writes option bytes, since some writes cannot be undone. Never halts or resets the target. Fails, with ST's reason, on a part the programmer has no option bytes for, such as the STM32N6.

NameTypeReqDescription
interfacestring––
probe_serial–––

Structured output declared, but exposes no named fields.

No examples provided.

release_probe ~127

Stop the GDB server holding a probe; with no serial, every probe's. Resumes a core run_until left halted. While held, the reading tools work beside the server, but a core that locks up is reset, clearing its fault registers. A program that closes the debug port closes it held or not; board_state then gets back in through a reset, restarting the program, except on an STM32N6 running ST's start-up code, which needs a power cycle. `unverified` if nothing was held.

NameTypeReqDescription
probe_serial–––

Structured output declared, but exposes no named fields.

No examples provided.

reset_target ~116

Reset the target and check that it restarted: the program counter is compared with the reset vector during a brief halt, which is reported, and the core is then left running from reset. Needs an open debug port: when the running program has closed it, board_state reconnects through a reset, and this tool does not. Stops a GDB server holding the probe first (`released_probe_first`). To stop the core somewhere, use run_until.

NameTypeReqDescription
interfacestring––
probe_serial–––

Structured output declared, but exposes no named fields.

No examples provided.

run_firmware ~167

Reset the target, load an ELF into its RAM, start it, and verify that it started: by its board's console output, or else by program-counter samples inside the image. Refuses an image not linked for RAM: vector table at board_state's `vector_table_addr`, every segment within 0x20000000-0x3FFFFFFF. Lets go of the probe once the program starts; `keep_probe=True` keeps a GDB server holding it, and a core that then locks up is reset, clearing its fault registers. No signing.

NameTypeReqDescription
console_secondsnumber––
elf_pathstringyes–
interfacestring––
keep_probeboolean––
probe_serial–––

Structured output declared, but exposes no named fields.

No examples provided.

run_until ~166

Run the target until it reaches `location` (a function, its inlined copies included, "file.c:line" or a "0x..." address) or writes `watch` (a variable, or a "0x..." address watched as 4 bytes), for at most `seconds`. The core is left halted where it stopped, with the call stack, until release_probe. Needs the ELF the target runs. Verified only when the chip's DFSR names the stop; a watchpoint stops just after the write. The rest of the chip keeps running.

NameTypeReqDescription
elf_pathstringyes–
interfacestring––
location–––
probe_serial–––
secondsnumber––
watch–––

Structured output declared, but exposes no named fields.

No examples provided.

sample_values ~201

Sample values while the program runs, without halting or resetting it: `what` lists variables (decoded with `elf_path`'s types; "g_state.mode" picks a member), "0x..." word addresses, or registers such as "ADC3.ISR" (`svd` and `read_effects_ok` as in read_memory). All are read together, a few times a second, for `seconds` (at most 60), with the core's state; each comes back with first, last, range and changes. `until`, such as "g_state.mode == MODE_RUN" or "g_ticks changes", stops early.

NameTypeReqDescription
elf_path–––
interfacestring––
probe_serial–––
read_effects_okboolean––
secondsnumber––
svd–––
until–––
whatarrayyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the stlink-mcp server?

stlink-mcp runs locally as a PyPI package, launched with uvx stlink-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · stlink-mcp

# add to Claude Code
claude mcp add dii-stlink-mcp -- uvx stlink-mcp
Common questions

What is the stlink-mcp server?

stlink-mcp is listed in the public MCP registry as io.github.dii/stlink-mcp. Program, run and inspect STM32 targets over ST-LINK; every result verified, unverified or failed. This page covers its PyPI package (stlink-mcp).

Is the stlink-mcp server safe to use?

stlink-mcp scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 stlink-mcp server expose?

stlink-mcp exposes 16 tools: list_probes, board_state, run_firmware, release_probe, flash_firmware, and 11 more. Their descriptions and schemas cost roughly 2,282 tokens of context every time the server is loaded.

Is the stlink-mcp server still maintained?

stlink-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 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 stlink-mcp server under?

stlink-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the stlink-mcp server?

VerifyMCP ran 15 checks on stlink-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about stlink-mcp: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.