io.github.Edge-Echo/mcp-netassist
NPM · MCP-NETASSIST · SCANNED OCT 5
Windows network and proxy diagnostics: GitHub reachability, proxy ports, DNS/TCP, and fixes.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 343 tokens (~57/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the io.github.Edge-Echo/mcp-netassist server?
io.github.Edge-Echo/mcp-netassist runs locally as an npm package, launched with npx -y mcp-netassist. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-netassist
claude mcp add edge-echo-mcp-netassist -- npx -y mcp-netassist
{
"mcpServers": {
"edge-echo-mcp-netassist": {
"command": "npx",
"args": [
"-y",
"mcp-netassist"
]
}
}
} {
"servers": {
"edge-echo-mcp-netassist": {
"command": "npx",
"args": [
"-y",
"mcp-netassist"
]
}
}
} codex mcp add edge-echo-mcp-netassist -- npx -y mcp-netassist
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"edge-echo-mcp-netassist": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-netassist"
],
"enabled": true
}
}
} openclaw mcp add edge-echo-mcp-netassist --command npx --arg -y --arg mcp-netassist
mcp_servers:
edge-echo-mcp-netassist:
command: "npx"
args: ["-y", "mcp-netassist"] {
"McpServers": {
"edge-echo-mcp-netassist": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-netassist"
]
}
}
} assistant mcp add edge-echo-mcp-netassist -t stdio -c npx -a -y mcp-netassist
{
"mcpServers": {
"edge-echo-mcp-netassist": {
"command": "npx",
"args": [
"-y",
"mcp-netassist"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Oct 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 9 Oct 2026 · Analysed npm/mcp-netassist@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
net_diag ~74
Full reachability diagnosis for any host: DNS resolution, TCP connect test, then an HTTP(S) status check.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname or IP address |
| path | string | – | URL path for the HTTP check (default /) |
| port | integer | – | TCP port to test (default 443) |
No output schema declared.
No examples provided.
net_doctor ~56
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
net_github_status ~36
Check whether github.com is reachable right now: DNS resolution, TCP 443, and the HTTPS status code with round-trip time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
net_hosts_check ~37
Scan the Windows hosts file for GitHub-related entries. Pinned entries bypass a proxy and can go stale — this lists what is pinned.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
net_proxy_probe ~89
Probe local proxy ports for TCP reachability. Defaults to the common ports (10808, 10809, 7890, 7897, 8888, 1080); pass `ports` to override.
| Name | Type | Req | Description |
|---|---|---|---|
| ports | array | – | Ports to probe (default 10808, 10809, 7890, 7897, 8888, 1080) |
No output schema declared.
No examples provided.
net_proxy_status ~51
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.Edge-Echo/mcp-netassist server?
io.github.Edge-Echo/mcp-netassist is listed in the public MCP registry as io.github.Edge-Echo/mcp-netassist. Windows network and proxy diagnostics: GitHub reachability, proxy ports, DNS/TCP, and fixes. This page covers its npm package (mcp-netassist).
Is the io.github.Edge-Echo/mcp-netassist server safe to use?
io.github.Edge-Echo/mcp-netassist scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Edge-Echo/mcp-netassist server expose?
io.github.Edge-Echo/mcp-netassist exposes 6 tools: net_github_status, net_proxy_status, net_proxy_probe, net_diag, net_hosts_check, net_doctor. Their descriptions and schemas cost roughly 343 tokens of context every time the server is loaded.
Is the io.github.Edge-Echo/mcp-netassist server still maintained?
io.github.Edge-Echo/mcp-netassist is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Edge-Echo/mcp-netassist server under?
io.github.Edge-Echo/mcp-netassist declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.