MCP Graphql vs Netdiag MCP

A side-by-side look at the MCP Graphql and Netdiag MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

MCP Graphql logoMCP GraphqlDeveloper Tools · Local subprocess (stdio)Model Context Protocol server for GraphQL57GoodAuth: no auth requiredNetdiag MCP logoNetdiag MCPDeveloper Tools · Local subprocess (stdio)MCP server wrapping dig, ping, mtr, whois and TLS/HTTP checks for on-demand network diagnostics52GoodAuth: not declared

Verdict: choose MCP Graphql 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?

MCP Graphql logoChoose MCP Graphql when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like introspect-schema, query-graphql.
Explore MCP Graphql

Netdiag MCP logoChoose 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.
Explore Netdiag MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Graphql logoMCP GraphqlNetdiag MCP logoNetdiag MCP
CategoryDeveloper ToolsDeveloper Tools
Quality signal57/100 · Good52/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars4080
Directory activity 5 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools212

Tools & capabilities

MCP Graphql tools 2

  • introspect-schemaThis tool retrieves the GraphQL schema. Use this first if you don't have access to the schema as a resource.
  • query-graphqlExecute GraphQL queries against the endpoint. By default, mutations are disabled unless `ALLOW_MUTATIONS` is set to `true`.

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/DoH
  • dnssec_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 it
  • ping_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 scan
  • http_checkHEAD/GET a URL and report status, redirect chain, and latency
  • http_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 redirect
  • tls_cert_checkFetch the certificate a host presents and report subject/issuer/validity/SANs
  • whois_lookupWHOIS lookup for a domain
  • asn_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 needed
  • current_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 check
  • health_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.

MCP Graphql

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "blurrah-mcp-graphql": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-graphql"
      ]
    }
  }
}

Netdiag MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "netdiag-mcp": {
      "command": "uvx",
      "args": [
        "netdiag-mcp"
      ]
    }
  }
}

Frequently asked questions

MCP Graphql is categorized under Developer Tools and uses a local stdio subprocess. Netdiag MCP belongs to Developer Tools and uses a local stdio subprocess. Pick MCP Graphql 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.

MCP Graphql is listed as free. Auth: no auth required. 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 blurrah-mcp-graphql and netdiag-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCP Graphql has a quality signal of 57/100 (Good) with 5 views, 0 installs and 408 GitHub stars. Netdiag MCP has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.