ai.dinglebear/unifi-rmcp
UniFi RMCP
Is the UniFi R MCP server down? Yes. It has given no valid answer since 2026-10-18: not found.
Rust MCP server and CLI for UniFi Network controller operations.
not found down since 2026-10-18 · probed 2026-11-15 · unchanged since 2026-11-01
npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete lo
- Run it
- npx -y unifi-rmcp@0.2.4 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/jmagar/unifi-rmcp
- Website
- https://github.com/jmagar/unifi-rmcp
- Registry
- active, updated 2026-07-12 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Soma ai.dinglebear/soma · crashed on start
- Synapse RMCP ai.dinglebear/synapse · needs env
- Synapse RMCP ai.dinglebear/synapse-rmcp · not found
- Tailscale RMCP ai.dinglebear/tailscale-rmcp · not found
- Unraid RMCP ai.dinglebear/unraid · needs env
- Unraid RMCP ai.dinglebear/unraid-rmcp · not found
- Yarr MCP ai.dinglebear/yarr · needs network
- Yarr MCP ai.dinglebear/yarr-mcp · not found
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-10-18, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.