
Mcp Netassist
io.github.Edge-Echov0.1.1Updated Oct 1, 2026
Windows network and proxy diagnostics: GitHub reachability, proxy ports, DNS/TCP, and fixes.
Installation
In SourceWeft
- Open Mcp Netassist in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-netassist
[npm version] [npm downloads] [license]
Part of the dsh-toolkit family: dsh-mcp-bridge · dsh-win-toolkit · dsh-netassist · dsh-driftwatch · mcp-netassist · dsh-ledger
Network & proxy diagnostics as an MCP server.
Works with any MCP client — Claude Code, Claude Desktop, Cursor, Reasonix, CodeWhale, DeepSeek Harness. Point your agent at it and ask "is GitHub reachable?", "why is my proxy not working?", "what should I change?" — instead of guessing.
Built for the China-network reality: flaky GitHub, proxies that are half-configured, hosts files that fight the proxy, and TUN mode that silently overrides the system proxy.
Windows-only for now: the checks call PowerShell. The protocol layer is portable; a POSIX backend is the obvious next step.
Platform
Windows. The checks read the system proxy from the Windows registry and shell out to
powershell.exe; on Linux and macOS the tools start but their checks cannot run, and they
report PowerShell failed: spawn powershell.exe ENOENT rather than pretending to have
checked something.
The packaging is portable (any MCP client can connect, the server speaks plain stdio), but the
diagnostics are Windows-specific today. A POSIX implementation would read the proxy from the
environment and use ss/lsof for port probing; that is not written yet, so the README says
Windows instead of implying otherwise.
Timing
Every check spawns a powershell.exe, and a cold one costs roughly 20 seconds to start. So on
a freshly booted Windows machine:
- the individual tools answer within about half a minute
net_doctorcan exceed a minute, because it runs four checks in parallel plus a port probe
Most MCP clients default to a 60-second request timeout, so net_doctor may time out on a cold
machine even though it is working. If that happens, call the individual checks (net_github_status,
net_proxy_status, net_hosts_check) instead, or raise your client's request timeout. Once
PowerShell has been used a few times the cost drops sharply.
Tools
net_doctor is the point of this server. Other tools tell you what is wrong; it tells you what to do about it:
Setup
Claude Desktop / Cursor / any JSON-configured client:
The built lib/ ships in the repository, so the GitHub form needs no build step.
From npm:
Claude Code:
DeepSeek Harness (same diagnostics as a native plugin, plus net_doctor as an agent tool):
From a checkout:
In a container:
The image is also what directory listings use for introspection checks. Inside a Linux container the server starts and answers
initialize/tools/listnormally; the tools themselves need Windows PowerShell, and say so when it is missing.
Design notes
- Read-only. No tool writes config, changes the proxy, or edits the hosts file. It reports and suggests; you decide.
- Injection-safe. Every user input crosses the PowerShell boundary as Base64, never as interpolated text.
- No hidden state. Each call runs its own checks; nothing is cached between calls, so results are always current.
- Two dependencies (
@modelcontextprotocol/sdk,zod), no native modules.
Related
Part of the dsh-toolkit family — the same diagnostics also ship as a DeepSeek Harness plugin (dsh-netassist), which adds net_doctor as an agent tool.
License
MIT
Source: README.md at commit b8f44e9
Tools
0Version history
1- v0.1.1LatestOct 1, 2026

