fleetcheck-mcp
The problem
When a store calls saying the internet is down, the first five minutes are always the same ritual: ping the gateway, check DNS, hit the health endpoint, test the VPN port, look at the TLS cert quietly counting down to expiry. Doing that by hand across a fleet is slow, and it is the part of the job least worth a human’s attention.
What I built
An MCP server that hands those checks to Claude as seven read-only tools — ping_host, dns_lookup, http_health, tcp_port_check, tls_cert_check, traceroute_host and a fleet_sweep that runs them across many hosts at once. Read-only by design: it can tell you what is broken, never change it. Input validation is its own module so hostnames and ports are checked before anything touches the network, and every parser is covered by tests.
The result
Published under MIT with CI green on Python 3.10+, 60 test functions across validators, parsers, checks and the server itself. It is the bridge between the two halves of my work — the outage playbook I actually run at work, packaged so an AI assistant can run it too.