DapBLOCK
Model Context Protocol (MCP) server that interacts with a Debugger
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
dap-mcp is an implementation of the Model Context Protocol (MCP) tailored for managing Debug Adapter Protocol (DAP) sessions. MCP provides a standardized framework to optimize and extend the context window of large language models, and in this project, it is used to enhance and streamline debugging workflows.
Features
- Debug Adapter Protocol Integration: Interact with debuggers using a standardized protocol.
- MCP Framework: Leverage MCP to optimize context and enhance debugging workflows.
- Rich Debugging Tools: Set, list, and remove breakpoints; control execution (continue, step in/out/next); evaluate expressions; change stack frames; and view source code.
- Flexible Configuration: Customize debugger settings, source directories, and other parameters via a JSON configuration file.
Installation
Prerequisites
- Python 3.10 or higher
- uv (optional, for running the server)
Installing and Running the Server
Install dap-mcp and its dependencies:
pip install dap-mcp python -m dap_mcp --config config.json # Or, if you have uv installed uvx dap-mcp@latest --config config.json
Configuration
The project uses a JSON configuration file (e.g., .config.json) to specify debugger settings and source directories. An example configuration:
{
"type": "debugpy",
"debuggerPath": "/path/to/python/with/debugpy",
"debuggerArgs": [
"-m",
"debugpy.adapter"
],
// source directories for resolving file paths
// if you always use absolute paths, you can omit this
"sourceDirs": [
"/path/to/source/code"
],
// debugger-specific settings start here
// configurations for debugpy can be found at
// https://github.com/microsoft/debugpy/wiki/Debug-configuration-settings
// you can use "program" instead of "module" to specify the program to debug
"module": "pytest",
// the python executable to use to run the 3c52835d3c52OBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add dap-mcp -- uvx dap-mcp
{
"mcpServers": {
"dap-mcp": {
"command": "uvx",
"args": [
"dap-mcp"
]
}
}
}Exposed tools (14)
8 read · 3 write · 3 destructive. Blast radius: 3 tools can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
change_frame | read | Change the current debugging frame to the specified frame ID. |
continue_execution | read | Continue execution in the debugger after hitting a breakpoint. |
evaluate | read | Evaluate an expression in the current debugging context. |
get_launch_config | read | Returns the user provided launch configuration along with its detailed schema for a DAP-compatible debugger. The schema includes descriptions for each field. |
launch | write | Launch the debuggee program. Set breakpoints before launching if necessary. |
list_all_breakpoints | write | List all breakpoints currently set in the debugger. |
next | read | Step over to the next line of code in the debugger. |
remove_all_breakpoints | destructive | Remove all breakpoints currently set in the debugger. |
remove_breakpoint | destructive | Remove a breakpoint from the specified file and line. |
set_breakpoint | write | Set a breakpoint at the specified file and line with an optional condition. |
step_in | read | Step into the function call in the debugger. |
step_out | read | Step out of the current function in the debugger. |
terminate | destructive | Terminate the current debugging session. |
view_file_around_line | read | Returns the lines of source code and the source code around the specified line. You should ALWAYS prefer this tool if you are reading code. Because it will show the line number, which is crucial for debugging. If |
Trust audit
BLOCKgrade D · trust 69/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | WARN |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (4)
sudo: bool = Field(
system use found in code, not declared in the description
remove_all_breakpoints, remove_breakpoint, terminate
.pre-commit-config.yaml
Gates applied: no_behavioural_pass.
3c52835d3c52full audit observations/trust-audit/mcp-server/kashuncheng__dap.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 3c52835d3c52 | BLOCK | D | 69 | first audit |
Questions
What is the Dap MCP server?
Model Context Protocol (MCP) server that interacts with a Debugger
What tools does Dap expose?
14 in total: 8 read-only, 3 that write, and 3 that can delete or overwrite (remove_all_breakpoints, remove_breakpoint, terminate). Every one is listed on this page with its risk.
Is Dap safe to connect to an agent?
No — not without reading the findings first. The audit graded it D (69/100) and found 1 critical or high issue in the source. Each one is listed on this page with the file and line it is on. Separately from the audit: 3 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does Dap need?
No credential environment variables were found in its source, so it appears to need none.
How does Dap run?
It speaks stdio, so it runs as a local process your client starts. It is published on PyPI as dap-mcp.
How current is this page?
The grade is for one exact copy of the source (3c52835d3c52), read on 2026-10-08. The repository is watched and re-audited when it changes.