stm32-stlink-mcp (phryniszak/stmcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 19 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

stm32-stlink-mcp

MCP server for debugging STM32 microcontrollers over ST-LINK using STM32CubeCLT tools (GDB, ST-LINK_gdbserver, STM32_Programmer_CLI) with session management, flashing, breakpoints, memory/register access, and expression evaluation.

→ phryniszak/stmcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

phryniszak

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Known vulnerabilities in dependencies: 1 critical
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
// known CVEs in dependencies1 critical

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@2.1.9GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configSTMCP_CUBECLT_PATHPATH (the CLT installer does this by default) or via / per-tool overrides.
configSTMCP_DEFAULT_DEVICEDefault MCU device string
configSTMCP_DEFAULT_FREQUENCY_KHZSWD/JTAG clock
configSTMCP_DEFAULT_INTERFACEswd or jtag
configSTMCP_FLASH_RANGE_ENDFlash address window for the write guard (default: 128KB, STM32G431CB)
configSTMCP_FLASH_RANGE_STARTFlash address window for the write guard (default: 128KB, STM32G431CB)
configSTMCP_GDBSERVER_READY_TIMEOUT_MSHow long to wait for "Waiting for debugger connection..."
configSTMCP_LOG_FILEOptional log file (stderr always used regardless — stdout is reserved for MCP framing)
configSTMCP_LOG_LEVELdebug
configSTMCP_MAX_FILE_SIZE_BYTESMax size for file arguments
configSTMCP_MAX_SESSIONSConcurrent debug session cap
configSTMCP_STLINK_SERIALDefault probe serial (omit to auto-select if exactly one is attached)
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

19/19 tools missing one or more hints — breakpoint_set (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); breakpoint_clear (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); breakpoint_list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +16 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 0/19 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/phryniszak/stmcp)](https://m8ven.ai/mcp/phryniszak/stmcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 0ccdcfc14b1e33d4029dd5c7597f9edc0259fcd9
code hash: 29f0d6adeb041c0e774a055c75fefbc916f3fac6e664c2dbdb2e0a4ca5fa2c93
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client