Web Network Tools
Run DNS lookup, WHOIS, SSL checks, and HTTP status from the agent using public APIs without scraping.
Overview
Web Network Tools is an MCP server for the Ship phase that runs DNS, WHOIS, SSL, and HTTP status checks via public APIs for release and security validation.
What is this MCP server?
- DNS lookup via public APIs
- WHOIS queries without custom scrapers
- SSL checker for certificate issues before go-live
- HTTP status tooling for uptime and redirect debugging
- stdio npm @erikirby/web-network-tools v1.0.0; no scraping
- Registry version 1.0.0
- npm package @erikirby/web-network-tools
- stdio MCP transport
What problem does it solve?
Indie developers lose time context-switching to terminal and browser tools when validating DNS, certs, and HTTP before launch.
Who is it for?
Solo builders shipping custom domains and HTTPS who want lightweight diagnostics inside the agent.
Skip if: Large-scale synthetic monitoring platforms that need global probes and paging on-call rotations.
What do I get? / Deliverables
Your agent can run standard network diagnostics in-thread so you fix misconfigurations before users hit them.
- DNS and WHOIS answers for domains you specify
- SSL validation results for pre-launch review
- HTTP status codes for endpoint and redirect checks
Recommended MCP Servers
Journey fit
How it compares
Diagnostic network MCP using public APIs, not full domain marketing intelligence.
Common Questions / FAQ
Who is Web Network Tools for?
Solo developers and small teams validating DNS, certificates, and HTTP responses during build and ship.
When should I use Web Network Tools?
Use it before launch for SSL and HTTP checks and during operate when debugging DNS or redirect issues.
How do I add Web Network Tools to my agent?
Register stdio MCP for @erikirby/web-network-tools from npm in Claude Code, Cursor, or Codex.