Pingo
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Pingosweep 192.168.1.0/24 and show me live hosts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Pingo - Local LAN Debugging MCP Server
An MCP server exposing a full toolkit for debugging your local network, wired through a clean service-per-concern architecture so it's easy to extend.
Tools exposed
Tool | What it does |
| Lists local IPv4 interfaces (name, IP, netmask, MAC) |
| Pings a single IPv4 address, reports alive/latency |
| Sweeps a |
| OS-native traceroute/tracert to a host or IP |
| Resolves a hostname to its IPv4/IPv6 addresses |
| Resolves an IP back to hostname(s) |
| Checks if a single TCP port is open |
| Scans a range of TCP ports (max 1024 span) via raw sockets |
| Reads the OS ARP cache -> IP-to-MAC mappings on the LAN |
| Lists active connections via |
| Checks if an HTTP(S) endpoint responds, with status + latency |
Related MCP server: connectivity-diagnostics
Design notes
One service per concern (
src/services/*) - each does exactly one job and is injected into the controller, so adding a new diagnostic (e.g. MTU discovery, bandwidth test) means adding one new service + oneregisterToolcall, nothing else changes.No shell injection surface. Every OS command runs through
execFile(argv array, never a shell string), and every input is validated against a strict allow-list (src/utils/validators.ts) before it ever reaches a command or socket.Bounded by default. Port scans cap at a 1024-port span, sweeps cap at
/24, everything has a timeout - so a bad input can't hang the process or turn into an unbounded network scan.DNS uses Node's native
dns/promises, not a shell command at all - one less exec surface for the riskiest-sounding tool.
Run it
pnpm install
pnpm dev # tsx src/index.ts, hot-reload dev mode
pnpm build && pnpm start # compiled prod runServer listens on http://localhost:3000/mcp.
Extending it
Add
src/services/YourService.tsimplementing anIYourServiceinterface (mirror the existing services - constructor-free, one focused method or two).Add it to
PingoServicesinPingoMcpController.tsand instantiate it insrc/index.ts.Add one
server.registerTool(...)block inregisterTools().
That's the whole extension surface - no other files need to change.
This server cannot be deployed
Maintenance
Related MCP Connectors
Utility tools for AI agents: hashing, text stats, validation, DNS, currency, GEO audits.
Monitors TLS/SSL certificate expiry, DNS resolution, and TCP port status for AI agents.
Discover, inspect and run 63,000+ agent tools from one balance. Pay per call, no subscriptions.
PDF, image, video, OCR, screenshot, SQL, QR and text tools for agents. No API key, no signup.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceProvides network operations tools such as ping, traceroute, DNS queries, and nmap scans via MCP, enabling network diagnostics and monitoring through natural language.14MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform real network diagnostics on the local machine, including ping, traceroute, DNS lookups, TLS checks, and more.MIT
- FlicenseNot gradedqualityDmaintenanceAggregates network operations tools such as retrieving local network configurations and scanning ports, enabling IT professionals to perform these tasks via natural language.-
- AlicenseAqualityBmaintenanceEnables AI agents to check the health of internet infrastructure and specific services, helping diagnose whether issues are local or external.36 npmISC