io.github.claytono/go-unifi-mcp
io.github.claytono/go-unifi-mcp
Is the io.github.claytono/go-unifi-mcp MCP server down? Yes. It has given no valid answer since 2026-11-04: crashed on start.
Manage UniFi sites, devices, clients, networks, port forwarding, DNS, and firewall
crashed on start down since 2026-11-04 · probed 2026-11-15 · unchanged since 2026-11-11
MCP error -32000: Connection closed UNIFI_VERIFY_SSL Verify SSL certificates (default: true) UNIFI_LOG_LEVEL go-unifi log level: disabled|trace|debug|inf
- Run it
- docker run -i --rm ghcr.io/claytono/go-unifi-mcp:v0.3.1 (stdio, probed in a container with the network off)
- Host
- ghcr.io
- Repository
- https://github.com/claytono/go-unifi-mcp
- Registry
- active, updated 2026-07-24 · registry entry
Compare this server with others.
More servers
Other registry entries on ghcr.io, the ones next to this name; all of them.
- TrueNAS SCALE io.github.cedricziel/truenas-mcp · not probed
- CityEngine Cloud io.github.cgajs/cityengine-mcp · alive
- WPGuard MCP io.github.cgallic/wpguard-mcp · not probed
- tollbooth io.github.chrzanowy/agent-tollbooth · not probed
- MCP Failure Lab io.github.cloudlabworks/mcp-failure-lab · alive
- codeDB Lens io.github.codedb-io/codedb-lens · needs args
- io.github.coe0718/deskbrid · alive
- CMDOP Machine Care io.github.commandoperator/cmdop-care · alive
Servers that mention unifi.
- Synlake ai.synlake/synlake · not MCP
- com.api2cart/mcp · needs auth
- com.apideck/mcp · alive
- Cavyro com.cavyro/cavyro · needs auth
- Consulate - AI Dispute Resolution (Crypto + Traditional + General) com.consulatehq/consulate · no DNS
- Danube AI com.danubeai/danube · needs auth
- Jinko MCP com.gojinko.mcp/jinko · alive
- com.jojapi/gpt-5 · not MCP
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-11-04, in every probe since then.
- The process exited on start before it answered initialize. The error output is above.