Nettools MCP Server

mcp-nettools PyPI v0.2.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for network diagnostics and service health checks — 235 tools spanning ping/DNS/port/traceroute/TLS plus reachability probes for ~180 self-hosted services (databases, queues, observability, *arr stack, and more)

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 92/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

high Shell/command execution in server code (src/mcp_nettools/server.py)MTC-SRC-002

In the server's implementation (`src/mcp_nettools/server.py:82`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: result = subprocess.run( ["ping", "-c", str(count), "-W", str(timeout), host], ca

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/mcp_nettools/server.py

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([check_security_headers, check_miniflux]) co-exist with external-action tools ([http_post]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [check_security_headers, check_miniflux] → sinks [http_post]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow check_security_headers → http_post

Tools 200

Each tool and what it can reach — statically extracted from the published source.

  • check_minifluxingests untrusted input
  • check_security_headersingests untrusted input
  • http_postnetwork egress
  • arp_tableno sensitive capability
  • bgp_lookupno sensitive capability
  • cert_checkno sensitive capability
  • cert_check_bulkno sensitive capability
  • check_actual_budgetno sensitive capability
  • check_adguardno sensitive capability
  • check_alertmanagerno sensitive capability
Show 190 more tools ↓
  • check_anythingllmno sensitive capability
  • check_appwriteno sensitive capability
  • check_archiveboxno sensitive capability
  • check_audiobookshelfno sensitive capability
  • check_autheliano sensitive capability
  • check_authentikno sensitive capability
  • check_baikalno sensitive capability
  • check_bazarrno sensitive capability
  • check_bitwardenno sensitive capability
  • check_bookstackno sensitive capability
  • check_calibre_webno sensitive capability
  • check_cassandrano sensitive capability
  • check_changedetectionno sensitive capability
  • check_clickhouseno sensitive capability
  • check_cockpitno sensitive capability
  • check_code_serverno sensitive capability
  • check_collaborano sensitive capability
  • check_consulno sensitive capability
  • check_couchdbno sensitive capability
  • check_dashdotno sensitive capability
  • check_directusno sensitive capability
  • check_discourseno sensitive capability
  • check_dkimno sensitive capability
  • check_dmarcno sensitive capability
  • check_docker_apino sensitive capability
  • check_docmostno sensitive capability
  • check_docusealno sensitive capability
  • check_dokuwikino sensitive capability
  • check_dozzleno sensitive capability
  • check_elasticsearchno sensitive capability
  • check_embyno sensitive capability
  • check_etcdno sensitive capability
  • check_filebrowserno sensitive capability
  • check_firefly_iiino sensitive capability
  • check_flaresolverrno sensitive capability
  • check_forgejono sensitive capability
  • check_freshrssno sensitive capability
  • check_frigateno sensitive capability
  • check_ghostno sensitive capability
  • check_giteano sensitive capability
  • check_gitlabno sensitive capability
  • check_gitnessno sensitive capability
  • check_glancesno sensitive capability
  • check_gotifyno sensitive capability
  • check_grafanano sensitive capability
  • check_gristno sensitive capability
  • check_grocyno sensitive capability
  • check_guacamoleno sensitive capability
  • check_headscaleno sensitive capability
  • check_healthchecksno sensitive capability
  • check_hedgedocno sensitive capability
  • check_homeassistantno sensitive capability
  • check_homepageno sensitive capability
  • check_hoppscotchno sensitive capability
  • check_immichno sensitive capability
  • check_influxdbno sensitive capability
  • check_invoiceninjano sensitive capability
  • check_jaegerno sensitive capability
  • check_jellyfinno sensitive capability
  • check_jellyseerrno sensitive capability
  • check_joplin_serverno sensitive capability
  • check_kafkano sensitive capability
  • check_karakeepno sensitive capability
  • check_kavitano sensitive capability
  • check_keycloakno sensitive capability
  • check_kimaino sensitive capability
  • check_komgano sensitive capability
  • check_kubernetes_apino sensitive capability
  • check_ldapno sensitive capability
  • check_leantimeno sensitive capability
  • check_lidarrno sensitive capability
  • check_limesurveyno sensitive capability
  • check_linkdingno sensitive capability
  • check_linkwardenno sensitive capability
  • check_listmonkno sensitive capability
  • check_lokino sensitive capability
  • check_matomono sensitive capability
  • check_matrix_synapseno sensitive capability
  • check_mattermostno sensitive capability
  • check_maybeno sensitive capability
  • check_mealieno sensitive capability
  • check_memcachedno sensitive capability
  • check_memosno sensitive capability
  • check_miniono sensitive capability
  • check_mongodbno sensitive capability
  • check_monicano sensitive capability
  • check_mqttno sensitive capability
  • check_mylar3no sensitive capability
  • check_n8nno sensitive capability
  • check_navidromeno sensitive capability
  • check_neo4jno sensitive capability
  • check_netbirdno sensitive capability
  • check_netdatano sensitive capability
  • check_nextcloudno sensitive capability
  • check_nfsno sensitive capability
  • check_nocodbno sensitive capability
  • check_ntfyno sensitive capability
  • check_nzbgetno sensitive capability
  • check_ollamano sensitive capability
  • check_onlyofficeno sensitive capability
  • check_open_webuino sensitive capability
  • check_openprojectno sensitive capability
  • check_opensearchno sensitive capability
  • check_outlineno sensitive capability
  • check_paperlessno sensitive capability
  • check_penpotno sensitive capability
  • check_photoprismno sensitive capability
  • check_piholeno sensitive capability
  • check_plankano sensitive capability
  • check_plausibleno sensitive capability
  • check_pocketbaseno sensitive capability
  • check_portainerno sensitive capability
  • check_postgresno sensitive capability
  • check_prometheusno sensitive capability
  • check_prowlarrno sensitive capability
  • check_qbittorrentno sensitive capability
  • check_rabbitmqno sensitive capability
  • check_radicaleno sensitive capability
  • check_ralllyno sensitive capability
  • check_rdpno sensitive capability
  • check_readarrno sensitive capability
  • check_redisno sensitive capability
  • check_sabnzbdno sensitive capability
  • check_scrutinyno sensitive capability
  • check_seafileno sensitive capability
  • check_searxngno sensitive capability
  • check_shiorino sensitive capability
  • check_sipno sensitive capability
  • check_smbno sensitive capability
  • check_snipe_itno sensitive capability
  • check_spfno sensitive capability
  • check_stirling_pdfno sensitive capability
  • check_syncthingno sensitive capability
  • check_tandoorno sensitive capability
  • check_tempono sensitive capability
  • check_traefikno sensitive capability
  • check_transmissionno sensitive capability
  • check_tubearchivistno sensitive capability
  • check_umamino sensitive capability
  • check_uptime_kumano sensitive capability
  • check_vaultno sensitive capability
  • check_vaultwardenno sensitive capability
  • check_victoriametricsno sensitive capability
  • check_vikunjano sensitive capability
  • check_vncno sensitive capability
  • check_wallabagno sensitive capability
  • check_whoogleno sensitive capability
  • check_wikijsno sensitive capability
  • check_windmillno sensitive capability
  • check_wordpressno sensitive capability
  • check_zipkinno sensitive capability
  • check_ziplineno sensitive capability
  • check_zookeeperno sensitive capability
  • dns_bulk_lookupno sensitive capability
  • dns_lookupno sensitive capability
  • dns_propagationno sensitive capability
  • dnssec_checkno sensitive capability
  • ftp_checkno sensitive capability
  • geolocationno sensitive capability
  • get_public_ipno sensitive capability
  • http_checkno sensitive capability
  • http_deleteno sensitive capability
  • http_patchno sensitive capability
  • http_putno sensitive capability
  • http_redirect_chainno sensitive capability
  • http_security_headersno sensitive capability
  • imap_checkno sensitive capability
  • local_portsno sensitive capability
  • mac_lookupno sensitive capability
  • mysql_checkno sensitive capability
  • network_interfacesno sensitive capability
  • ntp_checkno sensitive capability
  • pingno sensitive capability
  • ping_sweepno sensitive capability
  • pop3_checkno sensitive capability
  • port_checkno sensitive capability
  • port_scanno sensitive capability
  • reverse_dnsno sensitive capability
  • reverse_dns_bulkno sensitive capability
  • scan_common_portsno sensitive capability
  • smtp_checkno sensitive capability
  • snmp_checkno sensitive capability
  • speedtestno sensitive capability
  • ssh_checkno sensitive capability
  • subnet_infono sensitive capability
  • tcp_bannerno sensitive capability
  • tls_version_checkno sensitive capability
  • tracerouteno sensitive capability
  • wake_on_lanno sensitive capability
  • whoisno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.2.0 latest A 92/100 2 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-nettools/badge.svg)](https://mcptrustchecker.com/registry/mcp-nettools)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-nettools"><img src="https://mcptrustchecker.com/registry/mcp-nettools/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-nettools/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-nettools --online --registry pypi

Use the free API → How scoring works

More in Cloud & DevOps