ai.dinglebear/tailscale-rmcp
Tailscale RMCP
Is the Tailscale R MCP server down? Yes. It has given no valid answer since 2026-10-19: not found.
Rust MCP server and CLI for Tailscale devices, users, keys, policies, and auth.
not found down since 2026-10-19 · probed 2026-11-15 · unchanged since 2026-10-26
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 tailscale-rmcp@0.1.3 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/jmagar/tailscale-rmcp
- Website
- https://github.com/jmagar/tailscale-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.
- YTDL RMCP ai.dinglebear/rytdl · needs network
- Soma ai.dinglebear/soma · crashed on start
- Synapse RMCP ai.dinglebear/synapse · needs env
- Synapse RMCP ai.dinglebear/synapse-rmcp · not found
- UniFi RMCP ai.dinglebear/unifi-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
Servers that mention tailscale.
- Tailscale RMCP ai.dinglebear/rtailscale · needs auth
- Tailscale MCP by usefulapi io.usefulapi/tailscale · timeout
- Tailscale MCP Server io.github.itunified-io/tailscale · alive
- Tailscale Compute io.github.dylantirandaz/tailscale-compute · alive
- Tailscale MCP Server io.github.YawLabs/tailscale-mcp · alive
- Tailscale io.github.tailscale-mcp/tailscale-mcp · needs network
- Tailscale MCP io.github.TMHSDigital/tailscale-mcp · needs env
- Homeport io.github.CapitalX/homeport · not probed
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-19, 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.