MCP servers › io.github.Zeraissh › stm32-gdb-mcp

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.Zeraissh/stm32-gdb-mcp

Debug STM32 firmware on real hardware via GDB + OpenOCD/ST-Link/J-Link with decoded results. — the publisher's description

8 of 8 record checks metRead-only · tools listed 2026-10-23Topic: developer-tools · AI-classifiedversion 0.15.1PythonMITstandard input/output38 tools

Summary

io.github.Zeraissh/stm32-gdb-mcp is a local MCP server listed in the official MCP registry at version 0.15.1. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 38 tools, 0 resources and 0 prompts.

Record checks

8 of 8 record checks met · 1 does not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
met: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#14,604 of 15,112 packages by monthly downloads, tied with 8 others
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: PyPI · listed version current
License: MIT
Dependencies: no known high or critical advisories
Repository: public
Tools: 38
Described as changing data: 25 of 38 toolsAI-classified
Mainly works on: files and code on the machine it runs onAI-classified
Topic: developer-toolsAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

25 tools are described as changing something (start_debug_session, stop_debug_session, self_check, …): our AI model's reading of the descriptions, not something we tested. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-23
Mode: read-only (no tool calls)
Latest version: 0.15.1, published 2026-10-19 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-19 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-23
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.15.1 (published 2026-10-19).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

38tools

0resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on.

25 of 38 tools are described as changing something (creating, editing, deleting, sending or running).

start_debug_sessiondescribed as changing data
“Starts the specified GDB Server (openocd, stlink, jlink) and connects the GDB Client to it.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
8 inputs
- server_typestring“Type of debug server backend.”
- server_argsarray“Optional args for the server e.g.”
- probestring“Optional OpenOCD probe type: stlink, jlink, or cmsis-dap.”
- serialstring“Probe/ST-Link serial to select a specific board (for concurrent multi-target).”
- speed_khzinteger“OpenOCD adapter clock used when server_args are inferred (default 4000).”
- usb_locationstring“Select the probe by physical USB position, e.g.”
- hub_channelinteger“Take the probe on this hub channel, using the usb_location recorded for it in the profile's hub.map.”
- sessionstring“Optional debug-session name.”
stop_debug_sessiondescribed as changing data
“Stops the GDB client/server, variable tracking, and all active RTT/SWO/UART readers.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input
- sessionstring“Optional debug-session name.”
self_checkon 3 other serversdescribed as changing data
“Validates the link right after connecting: reads CPUID and DBGMCU IDCODE and checks byte order, that a real Cortex-M is present, and that the device matches the expected family (from the profile MCU …”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs
- expected_familystring“Expected MCU/family, e.g.”
- haltboolean“Halt the core before reading (default true).”
- sessionstring“Optional debug-session name.”
detect_probereads or searches
“Lists physical ST-Link, J-Link, and CMSIS-DAP probes currently connected over USB.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- sessionstring“Optional debug-session name.”
suggest_server_argscalculates or converts
“Returns the correct OpenOCD server_args for an MCU family + probe (e.g.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 1 required
- mcustringrequired“MCU or family, e.g.”
- probestring“Optional.”
- speed_khzinteger“Adapter clock in kHz (default 4000; 0 keeps the config default).”
- sessionstring“Optional debug-session name.”
batchon 22 other serversruns code or commandsdescribed as changing data
“Runs several tool calls in ONE round trip and returns ALL their full results — the fastest way to do a sequence of operations (e.g.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
3 inputs, 1 required
- stepsarrayrequired“Ordered tool calls, each {tool, args}.”
- stop_on_errorboolean“Stop at the first failing step (default false).”
- sessionstring“Optional debug-session name.”
callon 9 other serversruns code or commandsdescribed as changing data
“Invoke ANY stm32-gdb-mcp tool by name — including one that is NOT in your current tool list (clients with tool-count limits may hide some).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
3 inputs, 1 required
- toolstringrequired“Name of the tool to invoke.”
- argsobject“Arguments for that tool.”
- sessionstring“Optional debug-session name.”
call_readreads or searches
“Like call, but restricted to tools that only READ state — so it needs no approval prompt where call, which can reach anything, does.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- toolstringrequired“Name of the read-only tool to invoke.”
- argsobject“Arguments for that tool.”
- sessionstring“Optional debug-session name.”
tool_helpreads or searches
“Returns descriptions and complete schemas for full-surface tools, including tools hidden in compact mode.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
- namestring“Exact tool name.”
- querystring“Case-insensitive name/description search.”
- sessionstring“Optional debug-session name.”
mcp_inforeads or searches
“Identifies THIS running stm32-gdb-mcp server: release version, git commit, the package directory the code was imported from (plus the install root the git probe used), whether compact mode is hiding …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- sessionstring“Optional debug-session name.”
recover_sessiondescribed as changing data
“Recovers a dropped or wedged session: cleanly tears down the GDB client and server, then restarts the server (with retry/backoff for a busy probe) using the last start_debug_session arguments and rec…”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs
- escalateboolean“Allow hub data-line/power escalation when a plain retry fails (default true).”
- deepboolean“Add a long (2 s) power-off rung to drain bulk capacitance.”
- sessionstring“Optional debug-session name.”
build_firmwareruns code or commandsdescribed as changing data
“Builds firmware with Keil uVision (UV4), CMake, make, or a custom command, so the AI can rebuild after a fix.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
12 inputs, 1 required
- kindstringrequired“Toolchain to build with.”
- projectstring“keil: path to the .uvprojx/.uvproj project.”
- rebuildboolean“keil: rebuild all (-r) instead of incremental (-b).”
- uv4_pathstring“keil: path to UV4.exe (auto-detected if omitted).”
- build_dirstring“cmake: the configured build directory.”
- directorystring“make: directory containing the Makefile.”
- targetstring“Keil/CMake/make build target.”
- configstring“cmake: build config, e.g.”
- commandarray“custom: full argv to run.”
- cwdstring“Working directory for the build.”
- timeout_secnumber“Max build seconds (default 600).”
- sessionstring“Optional debug-session name.”

Show 26 more tools

load_symbolsdescribed as changing data
“Loads symbols from an ELF/AXF into the current GDB session WITHOUT flashing.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs
- elf_pathstring“Path to the ELF/AXF.”
- sessionstring“Optional debug-session name.”
flash_firmwareon 1 other serverdescribed as changing data
“Flashes a compiled firmware binary to the target.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
3 inputs, 1 required
- file_pathstringrequired“Absolute path to the compiled firmware file (e.g.”
- reset_runboolean“Reset and run after flashing (default true).”
- sessionstring“Optional debug-session name.”
reset_targeton 2 other serversdescribed as changing data
“Resets the target device.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
4 inputs, 1 required
- haltbooleanrequired“If true, halts the CPU immediately after reset.”
- strategystring“Optional reset strategy: default, under_reset, software, or cold (hub power cycle).”
- commandstring“Optional custom GDB monitor reset command.”
- sessionstring“Optional debug-session name.”
continue_executionon 1 other serverdescribed as changing data
“Resumes execution of the target device until the next breakpoint.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input
- sessionstring“Optional debug-session name.”
halt_executiondescribed as changing data
“Interrupts/halts the target device execution.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input
- sessionstring“Optional debug-session name.”
run_and_waitdescribed as changing data
“Resumes the target and waits, returning a structured stop event (reason, symbolized frame, breakpoint id, signal) or a timeout.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs
- timeout_secnumber“Max seconds to wait for a stop (default 10).”
- sessionstring“Optional debug-session name.”
debug_untildescribed as changing data
“One-call repro step: set an optional conditional/temporary breakpoint at a location, run, and return the stop event PLUS the decoded backtrace and innermost-frame locals.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
6 inputs, 1 required
- locationstringrequired“Where to break, e.g.”
- conditionstring“Optional C condition, e.g.”
- temporaryboolean“Auto-delete the breakpoint after the first hit (default true).”
- ignore_countinteger“Hits to ignore before stopping.”
- timeout_secnumber“Max seconds to wait (default 10).”
- sessionstring“Optional debug-session name.”
capture_statereads or searches
“One-call 'where am I': decoded core registers + a PC/LR/SP summary, the decoded backtrace, and the innermost-frame locals.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- sessionstring“Optional debug-session name.”
flash_and_rundescribed as changing data
“One-call bring-up: flash an ELF (loads symbols), reset-halt, set a temporary breakpoint at an entry point (default 'main'), run to it, and return the decoded stop context.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
7 inputs, 1 required
- file_pathstringrequired“Path to the ELF to flash.”
- run_tostring“Entry point to stop at (default 'main').”
- timeout_secnumber“Max seconds to wait (default 10).”
- hub_channelinteger“Start a session on the probe at this hub channel first, if none is running.”
- usb_locationstring“Same, but naming the USB position directly, e.g.”
- mcustring“Passed through when this call starts the session; falls back to the profile.”
- sessionstring“Optional debug-session name.”
run_for_durationdescribed as changing data
“Runs the target freely for a wall-clock duration, halts it, and returns one structured report with final frame/context and optional expression captures.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
6 inputs, 1 required
- duration_secnumberrequired“Seconds to let the target run freely.”
- thenstring“Action after duration (default halt).”
- captureobject
- sampleobject“Best-effort low-rate debugger polling while running; does not halt the target.”
- resume_afterboolean“Resume execution after capture (default false).”
- sessionstring“Optional debug-session name.”
read_variablereads or searches
“Reads the value of a C variable currently in scope.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- namestringrequired“Name of the variable to read.”
- sessionstring“Optional debug-session name.”
read_memoryon 11 other serversreads or searches
“Reads a block of memory from the target.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 2 required
- addressstringrequired“Hex address to read from, e.g., '0x20000000'.”
- lengthintegerrequired“Number of bytes to read.”
- sessionstring“Optional debug-session name.”
write_memoryon 3 other serverscreates or changes datadescribed as changing data
“Writes a value to a specific memory address.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
3 inputs, 2 required
- addressstringrequired“Hex address to write to, e.g., '0x20000000'.”
- valuestringrequired“Value to write, e.g., '0xFF' or '1234'.”
- sessionstring“Optional debug-session name.”
read_call_stackreads or searches
“Reads the call stack as a decoded list of frames {level, func, file, line, addr} plus a one-line summary.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
- include_rawboolean“Include the raw GDB transcript (default false).”
- sessionstring“Optional debug-session name.”
analyze_stackon 2 other serversreads or searches
“Reports stack used/free bytes and a clear overflow verdict for the halted core.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs
- stack_topstring“Top-of-stack address (hex).”
- stack_limitstring“Lowest valid stack address (hex).”
- stack_sizestring“Stack size in bytes (used as stack_top - stack_size if stack_limit omitted).”
- vector_table_addrstring“Vector table base for the initial MSP (default '0x08000000').”
- sessionstring“Optional debug-session name.”
reconstruct_fault_contextdescribed as changing data
“Reconstructs the full crash site after a HardFault: decodes fault registers, unwinds the auto-stacked exception frame from MSP/PSP via EXC_RETURN to recover the true faulting PC, and resolves it to s…”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input
- sessionstring“Optional debug-session name.”
read_peripheral_registerreads or searches
“Reads a peripheral register using its name from the loaded SVD.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 2 required
- peripheralstringrequired“Peripheral name (e.g., 'GPIOA').”
- registerstringrequired“Register name (e.g., 'ODR').”
- sessionstring“Optional debug-session name.”
get_sessionon 24 other serversreads or searches
“Returns this session's record by view: 'journal' (every tool call with args/ok/summary/duration; supports limit), 'timeline' (compact human-readable replay), or 'metrics' (per-tool call counts, succe…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
- viewstring“Which view (default journal).”
- limitinteger“journal: return only the most recent N entries.”
- sessionstring“Optional debug-session name.”
list_sessionson 47 other serversreads or searches
“Lists all debug target sessions (the 'default' one plus any named) with their liveness and port.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- sessionstring“Optional debug-session name.”
close_sessionon 19 other serversdescribed as changing data
“Closes a named debug session, tearing down its GDB client and server.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs, 1 required
- session_idstringrequired“Name of the session to close, e.g.”
- sessionstring“Optional debug-session name.”
report_issueon 26 other serverssends messagesdescribed as changing data
“Files a GitHub issue about an MCP problem from THIS session — auto-bundling the session journal, metrics, and MCP version into a structured report (via the gh CLI).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
5 inputs, 2 required
- titlestringrequired“Short issue title, e.g.”
- descriptionstringrequired“What you were doing and what went wrong.”
- envstring“Agent/IDE + model, e.g.”
- repostring“owner/repo to file under (default the MCP repo).”
- sessionstring“Optional debug-session name.”
run_scenarioon 3 other serversruns code or commandsdescribed as changing data
“Replays a declarative scenario — a list of {tool, args} steps — deterministically and returns a per-step pass/fail report.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
4 inputs
- stepsarray“Ordered steps, each {tool, args}.”
- pathstring“Path to a JSON scenario file (alternative to inline steps).”
- stop_on_failureboolean“Stop at the first failing step (default true).”
- sessionstring“Optional debug-session name.”
loggingdescribed as changing data
“Firmware log capture over a channel.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
12 inputs, 1 required
- actionstringrequired“Which operation to perform.”
- sessionstring“Optional debug-session name.”
- channelstring“Log channel.”
- commandstring“rtt/swo: executable to launch (rtt defaults to JLinkRTTClient).”
- argsarray“rtt/swo: command arguments.”
- filestring“swo: tail OpenOCD's ITM decode file (run setup_swo first) — no external decoder needed.”
- portstring“uart: serial port, e.g.”
- baudrateinteger“uart: baudrate (default 115200).”
- timeoutnumber“uart: read timeout seconds (default 0.1).”
- limitinteger“Max recent entries to return.”
- since_indexinteger“Only entries with index greater than this.”
- clearboolean“Clear returned entries after reading.”
breakpointon 1 other serverdescribed as changing data
“Breakpoint / watchpoint management.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
8 inputs, 1 required
- actionstringrequired“Which operation to perform.”
- sessionstring“Optional debug-session name.”
- locationstring“Location to break at, e.g., 'main', 'main.c:42', or '*0x08001000'.”
- conditionstring“Optional C expression; break only when it is non-zero, e.g.”
- temporaryboolean“If true, the breakpoint is deleted after its first hit.”
- ignore_countinteger“Number of hits to ignore before stopping.”
- breakpoint_idstring“ID of the breakpoint to delete (e.g., '1').”
- access_typestring“Read (r), Write (w), or Access (a).”
debug_profilecreates or changes datadescribed as changing data
“Active debug profile (mcu/elf/svd/probe).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
13 inputs, 1 required
- actionstringrequired“Which operation to perform.”
- sessionstring“Optional debug-session name.”
- mcustring
- boardstring
- probestring
- server_typestring
- server_argsarray
- elf_pathstring
- svd_pathstring
- project_rootstring
- hubobject“Programmable USB hub binding: {port, serial, channel, map, power_cycle, guard}.”
- notesstring
- mergeboolean“Deep-merge nested blocks (hub, rtt, uart, swo, reset, hil) into the stored ones instead of replacing them -- use it to add one key, e.g.”
hubmanages infrastructuredescribed as changing data
“Programmable USB hub: per-port power, USB2 data lines, cold boot, and V/I sampling.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
16 inputs, 1 required
- actionstringrequired“Which operation to perform.”
- sessionstring“Optional debug-session name.”
- statestring“Target state for the port.”
- channelinteger“1-based hub channel.”
- confirmboolean“Required to cut power/data when the guard is in confirm mode or a session is live.”
- exclusiveboolean“With state=on, disconnect every other port's data line.”
- off_msinteger“Milliseconds to hold power off (default 400).”
- settle_msinteger“Milliseconds to wait after restoring power (default 1500).”
- duration_secnumber“Sampling window; 0 (default) takes one snapshot.”
- interval_secnumber“Delay between samples (default 0.05).”
- all_channelsboolean“Sample every channel instead of just one.”
- applyboolean“Write the discovered map into the debug profile.”
- forceboolean“Run even though a GDB server is alive on this session.”
- settle_secnumber“Seconds to wait for USB re-enumeration per toggle (default 1.0).”
- portinteger“HTTP port on 127.0.0.1 (default 8765).”
- open_browserboolean“Also open the page in the default browser.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 38 tools
Says what it returns: 0% of 12 tools
States limits, defaults or errors: 0% of 31 tools
Says when to use it: 22% of 32 tools
Items covered per tool: 1.5 of 4 on average

Counted from the listing

Parameters with a description: 94% of 161
Tools with a description: 100% of 38
Typical description length: 276 characters

The tool set

Counted from the listing

Tools: 38
Size of the list: about 9,459 tokens for an agent to load (characters ÷ 4)
Naming: 33 of 38 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 38 of 38 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the PyPI package stm32-gdb-mcp

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "stm32-gdb-mcp": {
      "command": "uvx",
      "args": [
        "stm32-gdb-mcp==0.15.1"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "stm32-gdb-mcp": {
      "command": "uvx",
      "args": [
        "stm32-gdb-mcp==0.15.1"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "stm32-gdb-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "stm32-gdb-mcp==0.15.1"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"stm32-gdb-mcp","type":"stdio","command":"uvx","args":["stm32-gdb-mcp==0.15.1"]}'

Claude Code

claude mcp add --transport stdio stm32-gdb-mcp -- uvx stm32-gdb-mcp==0.15.1

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- uvx stm32-gdb-mcp==0.15.1

Optional settings the entry also lists (left out above): STM32_GDB_MCP_COMPACT.
This runs the publisher's code on your machine (uvx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 0.15.1
Latest stable: 0.15.1
Status: current
Withdrawn: no

Source: pypi.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (OSV.dev). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha256-5002c32999a5e1823…
License: MIT

Source: the package registry · 2026-10-23.

Usage

Downloads: 52 in the last month

Source: pypistats.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 0.15.1 on PyPI	Exists and can be installed	matches	PyPI · 2026-10-23
Repository github.com/Zeraissh/stm32-gdb-mcp	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.Zeraissh
GitHub owner: a personal account (Zeraissh)

Repository: github.com/Zeraissh/stm32-gdb-mcp
Stars: 0
Repository age: 91–180 days
Last push: 0–30 days ago
Archived: no
Security policy: SECURITY.md

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

8 of 8 record checks met · 1 does not apply

#14,604 of 15,112 packages by monthly downloads, tied with 8 others
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.Zeraissh/stm32-gdb-mcp

Answered from the data above

Is io.github.Zeraissh/stm32-gdb-mcp safe to install?

We do not rate servers as safe or unsafe. 8 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 25 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.Zeraissh/stm32-gdb-mcp been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.Zeraissh/stm32-gdb-mcp do?

It lists 38 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, send messages, run code or commands, manage infrastructure and calculate or convert. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.Zeraissh/stm32-gdb-mcp change or delete data?

25 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.Zeraissh/stm32-gdb-mcp publish a security policy?

Yes: its repository has a public security policy (github.com/zeraissh/stm32-gdb-mcp/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 0.15.1, the latest stable release on PyPI.

Where is the source code of io.github.Zeraissh/stm32-gdb-mcp?

In github.com/Zeraissh/stm32-gdb-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.kivanccakmak/yaverYaveralso has tools that calculates or converts, creates or changes data, runs code or commands, manages infrastructure, reads or searches, sends messagescompare with this one
io.github.yaver-io/yaverYaveralso has tools that calculates or converts, creates or changes data, runs code or commands, manages infrastructure, reads or searches, sends messagescompare with this one
ai.rokha/rokhaRokhaalso has tools that calculates or converts, creates or changes data, runs code or commands, manages infrastructure, reads or searches, sends messagescompare with this one
io.github.keefng8/homeshed-mcpHomeShedalso has tools that calculates or converts, creates or changes data, runs code or commands, manages infrastructure, reads or searches, sends messagescompare with this one
io.github.A9T9/uivision-mcpUi.Vision MCPalso has tools that creates or changes data, runs code or commands, manages infrastructure, reads or searches, sends messagescompare with this one
io.github.tomyud1/godot-mcpalso has tools that calculates or converts, creates or changes data, runs code or commands, reads or searches, sends messagescompare with this one

Active servers whose topic is also “developer-tools” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 10

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against

Does not apply to this server · 6

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
1,994 msConnected after 0 redirects.
Read the inventory: 38 tools, 0 resources, 0 prompts.
2,506 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

developer-tools

AI-classified · 2026-10-23

Pricing modelAI-classified

no value

The website listed in the registry is a code-hosting, package or marketplace page, not the product's own site.

Programming language

Python

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

experimental, tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

pypi

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sha256)

package registry · 2026-10-23

Signature / provenance

does not apply

PyPI publishes no registry signature or attestation equivalent to npm dist.signatures

Dependency advisories

none known

OSV.dev · 2026-10-23

Popularity

52 downloads a month

package registry · 2026-10-23

Publisher signals

owner: a personal account · repository age: 91–180 days · stars: 0–9

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.Zeraissh/stm32-gdb-mcp: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.Zeraissh/stm32-gdb-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.Zeraissh/stm32-gdb-mcp)](https://protocolprobe.com/mcp/servers/io.github.Zeraissh/stm32-gdb-mcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology