Home / MCP registry index / com.thenetworkery/network-tools

The Networkery

com.thenetworkery/network-tools in the official MCP registry. Endpoint https://thenetworkery.com/mcp.

The registry describes it as: DNS, email auth, TLS, BGP/RPKI, WHOIS and subnet tools with plain-English fixes, plus webhook URLs.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http network-tools https://thenetworkery.com/mcp

{
  "mcpServers": {
    "network-tools": {
      "url": "https://thenetworkery.com/mcp"
    }
  }
}

code --add-mcp '{"name":"network-tools","type":"http","url":"https://thenetworkery.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

domain_report dns_lookup dns_propagation dnssec nameserver_check email_auth email_headers spf_builder dmarc_builder blacklist ssl_check http_headers ct_search whois bgp rpki peeringdb reverse_dns port_check subnet_calculator ipv6_tools cidr_merge mcp_server_test mac_lookup dn42_registry dn42_free dn42_peering_config create_webhook_url list_webhook_requests get_webhook_request

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-02): 5fbfdbdb00989a73. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-thenetworkery-network-tools/badge.svg)](https://lazaretto.dev/mcp-registry/com-thenetworkery-network-tools)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Email MCP servers