netassist
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| net_github_statusA | Check whether github.com is reachable right now: DNS resolution, TCP 443, and the HTTPS status code with round-trip time. |
| net_proxy_statusA | Show the proxy configuration from HTTP_PROXY / HTTPS_PROXY / ALL_PROXY / NO_PROXY. There is no system-wide proxy switch on Linux or macOS, so the environment variables are the whole story. |
| net_proxy_probeB | Probe local proxy ports for TCP reachability. Defaults to the common ports (10808, 10809, 7890, 7897, 8888, 1080); pass |
| net_diagA | Full reachability diagnosis for any host: DNS resolution, TCP connect test, then an HTTP(S) status check. |
| net_hosts_checkA | Scan the Windows hosts file for GitHub-related entries. Pinned entries bypass a proxy and can go stale — this lists what is pinned. |
| net_doctorA | 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_dns_compareA | Ask AliDNS, DNSPod, Cloudflare and Google the same question and compare the answers. A poisoned or stale system resolver is invisible until another server disagrees — which is the usual reason a host "resolves but does not work". |
| net_registry_checkA | Check the npm registry npm is actually configured to use (environment, then ~/.npmrc, then the official default), plus the official one for comparison: TCP reachability and HTTP status. "npm install failed" usually starts here, not at GitHub. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
The tools are highly granular and specialized, making them largely distinct. However, there is a minor functional overlap between the general diagnostic tools (net_diag) and the specific, curated workflows (net_doctor), which could lead to confusion regarding which function to call first.
All tool names utilize a consistent 'net_' prefix and adhere strictly to snake_case. The naming convention clearly indicates the focus and action (e.g., `net_proxy_status`, `net_hosts_check`), providing high predictability.
Eight tools are appropriate for the scope of complex network diagnostics. The tools are highly focused and address distinct areas like DNS comparison, proxy probing, and general host checks, ensuring each tool provides unique value.
The toolset provides excellent coverage for reachability and configuration verification. However, it is missing advanced networking features such as performance measurement (latency/bandwidth) and deep system-level configuration checks beyond environment variables.