Netdiag MCP vs UI5 MCP Server

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

Netdiag MCP logoNetdiag MCPDeveloper Tools · Local subprocess (stdio)MCP server wrapping dig, ping, mtr, whois and TLS/HTTP checks for on-demand network diagnostics52GoodAuth: not declaredUI5 MCP Server logoUI5 MCP ServerDeveloper Tools · Local subprocess (stdio)MCP server for UI5 application development68GreatAuth: no auth required

Verdict: choose Netdiag MCP for developer tools work as a local process; choose UI5 MCP Server 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?

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

UI5 MCP Server logoChoose UI5 MCP Server 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 get_guidelines, run_ui5_linter, get_api_reference.
Explore UI5 MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecNetdiag MCP logoNetdiag MCPUI5 MCP Server logoUI5 MCP Server
CategoryDeveloper ToolsDeveloper Tools
Quality signal52/100 · Good68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars0104
Directory activity 0 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools1210

Tools & capabilities

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

UI5 MCP Server tools 10

  • get_guidelinesThis tool MUST be called once to retrieve UI5 guidelines before working on any UI5 (SAPUI5/OpenUI5) related task or project or creating a UI5 project. The guidelines provided by this tool MUST be followed to ensure best practices and avoid common pitfalls in UI5 development.
  • run_ui5_linterRun UI5 linter on a UI5 project to find and optionally fix UI5 related problems like the usage of deprecated API. After making changes, you should always run the linter again to verify that no new problems have been introduced.
  • get_api_referenceSearch the UI5 API reference for module names and symbols
  • get_project_infoGet general information about a local UI5 project.
  • create_ui5_appCreate a new basic SAPUI5 application implemented in TypeScript or JavaScript
  • get_version_infoGet version information for UI5 (OpenUI5 or SAPUI5)
  • get_integration_cards_guidelinesThis tool MUST be called once to retrieve Integration Cards guidelines before working on any Integration Card related task or creating an Integration Card. The guidelines provided by this tool MUST be followed to ensure best practices and avoid common pitfalls in Integration Cards development.Integration Cards are also called 'UI Integration Cards' or 'UI5 Integration Cards'.
  • create_integration_cardCreate a new Integration Card, UI Integration Card, or UI5 Integration Card
  • run_manifest_validationValidates UI5 manifest file. After making changes, you should always run the validation again to verify that no new problems have been introduced.
  • get_typescript_conversion_guidelinesThis tool MUST be called once before converting a UI5 (SAPUI5/OpenUI5) project from JavaScript to TypeScript. The instructions provided by this tool MUST be followed to ensure that the project setup and code is correctly converted.

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.

Netdiag MCP

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

UI5 MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-server-80": {
      "command": "npx",
      "args": [
        "-y",
        "@ui5/mcp-server"
      ]
    }
  }
}

Frequently asked questions

Netdiag MCP is categorized under Developer Tools and uses a local stdio subprocess. UI5 MCP Server belongs to Developer Tools and uses a local stdio subprocess. Pick Netdiag MCP for developer tools work and UI5 MCP Server 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.

Netdiag MCP has no declared pricing — check the project's own site. UI5 MCP Server is listed as free. Auth: no auth required. 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 netdiag-mcp and mcp-server-80 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Netdiag MCP has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. UI5 MCP Server has 68/100 (Great) with 3 views, 0 installs and 104 GitHub stars.