Argus vs Netdiag MCP
A side-by-side look at the Argus and Netdiag MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Argus for developer tools work as a local process; choose Netdiag MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Argus when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
argus_audit, argus_audit_full, argus_compare.
Choose Netdiag MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
dns_lookup, dnssec_check, ping_host.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 57/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 9 | 12 |
| Full listing | View Argus | View Netdiag MCP |
Tools & capabilities
Argus tools 9
argus_auditFast pass — JS, network, accessibility, SEO, security, CSS, contentargus_audit_fullDeep pass — adds Lighthouse, responsive checks, memory leak detection, hover-state bugsargus_compareDiff dev vs staging — screenshots, findings delta, environment regressionsargus_get_contextCapture everything broken on the open tab — with `resolved / new / persisting` diff vs the last snapshot (the fix loop)argus_watch_snapshotSnapshot the open tab without navigating (preserves auth/form state)argus_last_reportReturn last JSON report without re-runningargus_design_auditFigma URL → 13 design-token finding types (color, spacing, typography, shadows, etc.)argus_visual_diffScreenshot baseline comparison. Pass `updateBaseline: true` to reset.argus_pr_validateFetch GitHub PR diff → map changed files to affected routes → targeted audit → baseline-aware block decision (blocks on findings the PR *introduces*) + idempotent PR comment + Check Run → `{ blocked, findings, baseline, reporting }
Netdiag MCP tools 12
dns_lookupResolve a DNS record via `dig` (A/AAAA/MX/TXT/NS/CNAME/SOA/PTR/CAA), optionally against a specific resolver and over plain DNS/DoT/DoHdnssec_checkQuery a known-validating resolver and report whether the AD bit is set (plain/DoT/DoH) — the only reliable way to confirm DNSSEC validation, since an RRSIG being present in a plain `dig` reply does not by itself prove anything validated itping_hostICMP ping (count clamped to 1-10)traceroute_pathHop-by-hop path/loss report via `mtr --report` (fixed cycles, not a live/continuous run)tcp_port_checkIs a TCP port open — a plain socket connect, not a port scanhttp_checkHEAD/GET a URL and report status, redirect chain, and latencyhttp_getGET a URL and return the body. Textual types only (`text/*`, JSON, XML, JavaScript, YAML, `+json`/`+xml`), capped at 1 MiB. Refuses loopback, link-local and cloud-metadata destinations, including via redirecttls_cert_checkFetch the certificate a host presents and report subject/issuer/validity/SANswhois_lookupWHOIS lookup for a domainasn_lookupASN + country-code lookup for an IP, or org info for an AS number, via Team Cymru's whois service — no API key or GeoIP database neededcurrent_timeCurrent date, time and weekday in an IANA timezone — the weekday is returned as data because deriving it from a date is arithmetic that fails silently. Also reports UTC and epoch, so it doubles as a clock checkhealth_checkVersion and which wrapped binaries (`dig`/`ping`/`mtr`/`whois`) are present on PATH
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Argus
{
"mcpServers": {
"argus-2": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
]
}
}
}
Netdiag MCP
{
"mcpServers": {
"netdiag-mcp": {
"command": "uvx",
"args": [
"netdiag-mcp"
]
}
}
}
Frequently asked questions
Argus is categorized under Developer Tools and uses a local stdio subprocess. Netdiag MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Argus for developer tools work and Netdiag MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Argus has no declared pricing — check the project's own site. Netdiag MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add argus-2 and netdiag-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Argus has a quality signal of 57/100 (Good) with 1 views, 0 installs and 5 GitHub stars. Netdiag MCP has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.