Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Klievan/jlink-mcpInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/klievan/jlink-mcp/jlink)<a href="https://agentmods.dev/mcp/klievan/jlink-mcp/jlink"><img src="https://agentmods.dev/badge/mcp/klievan/jlink-mcp/jlink/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/klievan/jlink-mcp/jlink"><img src="https://agentmods.dev/badge/mcp/klievan/jlink-mcp/jlink.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
jlink scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"jlink": {
"command": "node",
"args": [
"out/mcp/standalone.js"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 8 lines scan A 11f4c14a5824
jlink is an MCP server published in the GitHub repository Klievan/jlink-mcp (39 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
qwen-dap-mcp
Native runtime debugging via DAP-to-MCP for crashes, hangs, dumps, symbols, and forensics. Runs locally from the @slp-dev1/qwen-dap-mcp npm package.
x64dbg
MCP server for x64dbg debugger - 23 mega-tools for AI-powered reverse engineering and debugging. Runs locally from the x64dbg-mcp-server npm package. Needs 2 environment variables to run.
hardware-logging
MCP server "hardware-logging" as configured in gurul/hardware-logging. Runs locally from the hardware-logging Python package.
byteask-embedded-docs
MCP server "byteask-embedded-docs" as configured in ByteAsk/ByteAsk-Embedded-MCP. Runs locally from the byteask-embedded-mcp Python package.
embedded-docs
Page-cited retrieval for embedded docs, datasheets, MISRA, CMSIS, and RTOS references. Remote server at mcp.byteask.ai.
jdbg
MCP server "jdbg" as configured in PieceOfFall/jdbg. Launched with jdbg __mcp.