Tailscale RMCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track identity, package activity, privileges, documentation and data handling

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Tailscale tailnet operations over MCP

What we know

Control Tailscale devices, routes, keys, DNS and ACL using a local CLI/MCP bridge. Tailscale device, route, DNS, key, user, and ACL management over MCP and CLI.

Maintenance / activity evidence

215 downloads from 2026-09-09 through 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium_identity_and_metrics; published-function claims not execution verified.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
High-privilege network management; device deletion and policy changes are possible; apply least-privilege API key. Reported action classes: Review or change routing and ACL policy. Complete write authority is not verified.
See package authentication documentation; not independently tested.
Sensitive access: Account or infrastructure data accessible with supplied credentials

High-privilege network management; device deletion and policy changes are possible; apply least-privilege API key.
Public listing does not imply a safe runtime or security audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 215 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @dinglebear/rtailscale; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T17:26:34Z.

All limitations / Review context

Have @dinglebear/rtailscale permissions, hosted data retention, publication identity or supported MCP operations changed?

Bounded public tracking review; known consequences disclosed: High-privilege network management; device deletion and policy changes are possible; apply least-privilege API key.

High-privilege network management; device deletion and policy changes are possible; apply least-privilege API key.
Public listing does not imply a safe runtime or security audit.
See package authentication documentation; not independently tested.
Reviewed write actions: Review or change routing and ACL policy
Sensitive access: Account or infrastructure data accessible with supplied credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Operator must review permissions and remote data processing before installation.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Original activity observations

215 downloads from 2026-09-09 through 2026-10-08

Technical identity

npm/@dinglebear/rtailscale

Exact implementation source: https://www.npmjs.com/package/@dinglebear/rtailscale ↗
Reviewed resource type: MCP Server
Package identity: npm:@dinglebear/rtailscale

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Package registry ↗
@dinglebear/rtailscale
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Tailscale management gateway with TAILSCALE_API_KEY; API scope and tailnet configuration matter.
publisher install or stdio launch · Publisher instructions
npx -y @dinglebear/rtailscale mcp
Configure / authenticate
MCP100 setup guide
Publisher: `npx -y @dinglebear/rtailscale mcp` with TAILSCALE_API_KEY.
Check connection
Suggested check
`npx -y @dinglebear/rtailscale devices --json` is a read-only upstream check; do not modify ACLs or devices.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `dinglebear-rtailscale`, run `claude mcp remove dinglebear-rtailscale`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove dinglebear-rtailscale

Official Documentation & Sources

What it does

Control Tailscale devices, routes, keys, DNS and ACL using a local CLI/MCP bridge. Tailscale device, route, DNS, key, user, and ACL management over MCP and CLI.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Tailscale tailnet operations over MCP

Representative uses

Inspect tailnet devices
Review or change routing and ACL policy

Limitations

High-privilege network management; device deletion and policy changes are possible; apply least-privilege API key.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: See package authentication documentation; not independently tested.
Permissions: High-privilege network management; device deletion and policy changes are possible; apply least-privilege API key.
Data handling: High-privilege network management; device deletion and policy changes are possible; apply least-privilege API key.
Cost: Not verified; check vendor terms
Risk and cautions: High-privilege network management; device deletion and policy changes are possible; apply least-privilege API key.

Access scope and cautions

Write actions: Not verified Review or change routing and ACL policy
Sensitive access: Account or infrastructure data accessible with supplied credentials
Risk level: high
Security notes: High-privilege network management; device deletion and policy changes are possible; apply least-privilege API key. Public listing does not imply a safe runtime or security audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T17:26:34Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Inspect tailnet devices; Review or change routing and ACL policy.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded transport: stdio. Client notes: Never infer missing startup flags or credentials. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: API credential or authenticated app account required; exact setup should be checked in upstream package

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Review or change routing and ACL policy. Recorded permission context: High-privilege network management; device deletion and policy changes are possible; apply least-privilege API key.

What data-handling boundary should I consider?

High-privilege network management; device deletion and policy changes are possible; apply least-privilege API key. Recorded sensitive-access context: Account or infrastructure data accessible with supplied credentials.

What limitations and risks should I check before use?

High-privilege network management; device deletion and policy changes are possible; apply least-privilege API key. Exact install command and full env contract unverified except where explicitly documented; check official package before running. Exact npm download observation only; no independent installation test. Public listing does not imply a safe runtime or security audit. Operator must review permissions and remote data processing before installation.