Jlink (cyj0920) MCP Server
jlink-mcp
PyPI
v0.1.1
Published by cyj0920 — 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.
AI 与 JLink 调试器的桥梁 - MCP 服务器
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 − 6.3 = 94. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Unsafe deserialization MTC-SRC-007 | permissions |
2. Client adoption risk — 94 − 7 = 87. 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:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −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 2
high Shell/command execution in server code (src/jlink_mcp/gdb_server.py)MTC-SRC-002
In the server's implementation (`src/jlink_mcp/gdb_server.py:125`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: self._process = subprocess.Popen( cmd, stdout=subprocess.PIPE, s
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/jlink_mcp/gdb_server.py
medium Unsafe deserialization (src/jlink_mcp/svd_manager.py)MTC-SRC-007
In the server's implementation (`src/jlink_mcp/svd_manager.py:126`): Deserializing untrusted data with these APIs can execute arbitrary code (a well-known RCE gadget class). This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: device = pickle.load(f) logger.info(f"从缓存加载 SVD: {device_name}") return d
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/jlink_mcp/svd_manager.py
Tools 41
Each tool and what it can reach — statically extracted from the published source.
clear_breakpointno sensitive capabilityconnect_deviceno sensitive capabilitydisconnect_deviceno sensitive capabilityerase_flashno sensitive capabilityget_best_practicesno sensitive capabilityget_connection_statusno sensitive capabilityget_cpu_stateno sensitive capabilityget_forbidden_operationsno sensitive capabilityget_gdb_server_statusno sensitive capabilityget_svd_peripheralsno sensitive capability
Show 31 more tools ↓
get_svd_registersno sensitive capabilityget_system_promptno sensitive capabilityget_target_infono sensitive capabilityget_target_voltageno sensitive capabilityget_usage_guidanceno sensitive capabilityhalt_cpuno sensitive capabilitylist_device_patchesno sensitive capabilitylist_jlink_devicesno sensitive capabilitylist_scenariosno sensitive capabilitylist_svd_devicesno sensitive capabilitymatch_chip_nameno sensitive capabilityparse_register_valueno sensitive capabilityprogram_flashno sensitive capabilityread_memoryno sensitive capabilityread_register_with_fieldsno sensitive capabilityread_registersno sensitive capabilityreset_targetno sensitive capabilityrtt_get_statusno sensitive capabilityrtt_readno sensitive capabilityrtt_startno sensitive capabilityrtt_stopno sensitive capabilityrtt_writeno sensitive capabilityrun_cpuno sensitive capabilityscan_target_devicesno sensitive capabilityset_breakpointno sensitive capabilitystart_gdb_serverno sensitive capabilitystep_instructionno sensitive capabilitystop_gdb_serverno sensitive capabilityverify_flashno sensitive capabilitywrite_memoryno sensitive capabilitywrite_registerno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (41 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.1 latest |
B 87/100 | 2 | 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.
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 jlink-mcp --online --registry pypiOther implementations of Jlink 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.