MCP.Market

Netassist MCP server

by Edge-Echo·io.github.Edge-Echo/mcp-netassist·v0.1.1·1 stars
No reviews yet

Windows network and proxy diagnostics: GitHub reachability, proxy ports, DNS/TCP, and fixes.

A89/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A89/100

full report

Adoption
Growing

1 stars60 downloads/wk

Reviews

Write one

Nobody has reviewed Netassist yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Netassist tools (6, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • net_diag

    Full reachability diagnosis for any host: DNS resolution, TCP connect test, then an HTTP(S) status check.

  • net_doctorwrite action

    Run the full network preflight (system proxy, proxy ports, TUN adapters, GitHub reachability, hosts conflicts) and report each finding with concrete suggestions about what to change. Use this before blaming the network for a failure.

  • net_github_status

    Check whether github.com is reachable right now: DNS resolution, TCP 443, and the HTTPS status code with round-trip time.

  • net_hosts_check

    Scan the Windows hosts file for GitHub-related entries. Pinned entries bypass a proxy and can go stale — this lists what is pinned.

  • net_proxy_probe

    Probe local proxy ports for TCP reachability. Defaults to the common ports (10808, 10809, 7890, 7897, 8888, 1080); pass `ports` to override.

  • net_proxy_status

    Show the Windows system proxy configuration (registry) and proxy environment variables. Distinguishes "system proxy" from "TUN mode" from "no proxy", and flags a disabled-but-leftover registry value.

Public scan report

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

no findings
  • Code scan7 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Netassist compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
89/100
higher than 80% of 1,119 Developer tools servers
Tools
6
the typical Developer tools server has 7
Tools that change things
17%
typical: 5%. Fewer write tools means less an agent can break
GitHub stars
1
more than 50% of 855 Developer tools servers
Downloads a week
60
more than 44% of 436 Developer tools servers with a package

What its tools let an agent do: 5 read · 1 change

Install Netassist in Claude Code, Cursor or VS Code

Runs npx -y mcp-netassist on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-netassist -- npx -y mcp-netassist
Add to Cursor

What the publisher says

From the Netassist repository's README, as published. We do not edit it. Read it on GitHub

mcp-netassist

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:

probe

  • the individual tools answer within about half a minute
  • netdoctor can exceed a minute**, because it runs four checks in parallel plus a port

Most MCP clients default to a 60-second request timeout, so netdoctor may time out on a cold machine even though it is working. If that happens, call the individual checks (netgithubstatus, netproxystatus, nethosts_check) instead, or raise your client's request timeout. Once PowerShell has been used a few times the cost drops sharply.

Tools

netdoctor is the point of this server. Other tools tell you what is wrong*; it tells you what to do about it:

✔ System proxy: 127.0.0.1:10808
✔ Proxy port 10808 responding
✔ GitHub reachable (HTTP 200, 312 ms)
⚠ TUN-style adapter detected: clash
   Under TUN mode the system proxy setting is usually ignored — the two can fight each other.
✔ hosts file clean (no GitHub entries)

Suggested fix:
- Under TUN mode, clear the Windows system proxy (or exclude github.com) so traffic is not double-handled.

Setup

Claude Desktop / Cursor / any JSON-configured client:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Netassist: common questions

Is Netassist MCP server safe?
Yes, by our scan: it is graded A (89/100). Read the Netassist safety report
How do I install Netassist?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Netassist need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Netassist maintained?
The last commit was 34 days ago (2026-10-01). The latest release is v0.1.1.
What can I use instead of Netassist?
Servers from other publishers that do the same job: GitDiagram MCP server, GitHub MCP server and Gk CLI MCP server.
How does Netassist compare with other Developer tools MCP servers?
safety score 89/100 (higher than 80% of 1,119 Developer tools servers); tools 6 (the typical Developer tools server has 7); tools that change things 17% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Netassist

Same job from other publishers: the closest match first, then the best rated.

  • GitDiagram
    Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
    A
  • GitHub
    Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
    A
  • Gk CLI
    The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.
    B
  • Agent Harnesses
    Agent-harness picks, decision guides, setup templates, and skills; live GitHub/HN discovery.
    A
  • Porkbun (official)
    Official Porkbun MCP server: domains, DNS, SSL, hosting and Cloudflare via the Porkbun API.
    A