# stlink-mcp (pypi · stlink-mcp)

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

- Trust score: 73/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `stlink-mcp`: 73/100 (this document), [markdown](https://verifymcp.io/servers/dii-stlink-mcp/stlink-mcp.md), [page](https://verifymcp.io/servers/dii-stlink-mcp/stlink-mcp)

## Channel facts

- Registry: `pypi`
- Package: `stlink-mcp`
- Version: `0.9.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 93/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - 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.
  - 2 of 30 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to dii/stlink-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 12 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## 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.

### Claude

```bash
claude mcp add dii-stlink-mcp -- uvx stlink-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dii-stlink-mcp": {
      "command": "uvx",
      "args": [
        "stlink-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dii-stlink-mcp": {
      "command": "uvx",
      "args": [
        "stlink-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dii-stlink-mcp -- uvx stlink-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dii-stlink-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "stlink-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dii-stlink-mcp --command uvx --arg stlink-mcp
```

### Hermes

```yaml
mcp_servers:
  dii-stlink-mcp:
    command: "uvx"
    args: ["stlink-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dii-stlink-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "stlink-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dii-stlink-mcp -t stdio -c uvx -a stlink-mcp
```

### Other

```json
{
  "mcpServers": {
    "dii-stlink-mcp": {
      "command": "uvx",
      "args": [
        "stlink-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 73, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-17 (score 58, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-16 (score 73, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-15 (score 58, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-14 (score 73, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-13 (score 58, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-12 (score 73, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-11 (score 58, −15)

- [security regression] Malware scan: pass → unverified

## MCP tools (16)

### `list_probes` (~91 tokens)

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`.

### `board_state` (~145 tokens)

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.

Input parameters:

- `elf_path`
- `interface` (string)
- `probe_serial`

### `run_firmware` (~167 tokens)

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.

Input parameters:

- `console_seconds` (number)
- `elf_path` (string, required)
- `interface` (string)
- `keep_probe` (boolean)
- `probe_serial`

### `release_probe` (~127 tokens)

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.

Input parameters:

- `probe_serial`

### `flash_firmware` (~140 tokens)

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.

Input parameters:

- `address`
- `image_path` (string, required)
- `interface` (string)
- `probe_serial`

### `read_memory` (~195 tokens)

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.

Input parameters:

- `address`
- `elf_path`
- `interface` (string)
- `length_bytes` (integer)
- `probe_serial`
- `read_effects_ok` (boolean)
- `register`
- `svd`
- `symbol`

### `sample_values` (~201 tokens)

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.

Input parameters:

- `elf_path`
- `interface` (string)
- `probe_serial`
- `read_effects_ok` (boolean)
- `seconds` (number)
- `svd`
- `until`
- `what` (array, required)

### `run_until` (~166 tokens)

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.

Input parameters:

- `elf_path` (string, required)
- `interface` (string)
- `location`
- `probe_serial`
- `seconds` (number)
- `watch`

### `reset_target` (~116 tokens)

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.

Input parameters:

- `interface` (string)
- `probe_serial`

### `core_registers` (~135 tokens)

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.

Input parameters:

- `elf_path`
- `interface` (string)
- `probe_serial`

### `read_fault_status` (~129 tokens)

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.

Input parameters:

- `interface` (string)
- `probe_serial`

### `read_option_bytes` (~125 tokens)

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.

Input parameters:

- `interface` (string)
- `probe_serial`

### `locate_fault` (~134 tokens)

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.

Input parameters:

- `elf_path`
- `interface` (string)
- `probe_serial`

### `disassemble` (~139 tokens)

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.

Input parameters:

- `elf_path` (string, required)
- `interface` (string)
- `location` (string, required)
- `probe_serial`

### `capture_console` (~126 tokens)

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.

Input parameters:

- `probe_serial`
- `seconds` (number)

### `capture_swo` (~146 tokens)

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.

Input parameters:

- `core_clock_hz` (integer, required)
- `itm_port` (integer)
- `probe_serial`
- `seconds` (number)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/dii-stlink-mcp/stlink-mcp#diagnostics

## Score history

- 2026-11-21: 73
- 2026-11-20: 58
- 2026-11-19: 58
- 2026-11-18: 58
- 2026-11-17: 58
- 2026-11-16: 73
- 2026-11-15: 58
- 2026-11-14: 73
- 2026-11-13: 58
- 2026-11-12: 73
- 2026-11-11: 58
- 2026-11-10: 73
- 2026-11-09: 58
- 2026-11-08: 53

## 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.

## Links

- PyPI project: https://pypi.org/project/stlink-mcp/
- Socket report: https://socket.dev/pypi/package/stlink-mcp
- Repository: https://github.com/dii/stlink-mcp
- Changelog RSS feed: https://verifymcp.io/servers/dii-stlink-mcp/stlink-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dii-stlink-mcp/stlink-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dii-stlink-mcp/stlink-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dii-stlink-mcp/stlink-mcp
