T

Tailscale RMCP

ai.dinglebear/tailscale-rmcp · v0.1.3 · MCP server

by ai.dinglebearScan grade: AcceptableOfficial MCP registry · source scanned

Rust MCP server and CLI for Tailscale devices, users, keys, policies, and auth.

Protect this install with HOL Guard

Guard checks the skills and MCP servers a plugin adds on your machine and asks you before a risky action runs. The scores above are free, and no plan changes them.

Is Tailscale RMCP a fit?

From the plugin's manifest and HOL's scan. Anything the plugin does not declare is shown as not declared.

Works with

  • MCP
  • 1 MCP server

Before you install

Sign-in
Not declared
Declared access
Not declared
License
Not declared

Check before relying on it

  • Some security checks did not finish: Cisco skill scan and Cisco MCP scan. See the evidence
  • 1 high or critical finding from the scan. See the evidence
  • The publisher has not verified ownership on HOL.
  • No license declared in the manifest.

What is Tailscale RMCP?

Tailscale RMCP is a published mcp server plugin for AI coding agents in the MCP ecosystem, developed by ai.dinglebear and distributed through the HOL AI plugin registry. Rust MCP server and CLI for Tailscale devices, users, keys, policies, and auth.

Canonical slug
ai.dinglebear/tailscale-rmcp
Version
v0.1.3 · updated Jul 12, 2026

Registry snapshot

Owner verification
Not verified
Scanner
HOL plugin scanner
Security result
Needs review
Digest verified
No

Trust and security

Provenance

Plugin root
.
Source repo
https://github.com/jmagar/tailscale-rmcp
Source commit
c8859f1efe3e…
Publisher verified
No
Owner verified
Not owner verified
Needs review
Security result
70
Security score
1
High findings
Provider
codex-plugin-scanner
Grade
C · Acceptable
Version
3.24.2
codex:tailscale / cisco-skill-scanner: failedcodex:tailscale / cisco-mcp-scanner: unavailable

[claude:plugins/tailscale] Claude Plugin

13/18

5 checks

[claude:plugins/tailscale] Security

14/20

6 checks

[claude:plugins/tailscale] Operational Security

N/A

5 checks · not applicable

[claude:plugins/tailscale] Code Quality

10/10

2 checks

[codex:plugins/tailscale] Manifest Validation

20/31

9 checks

[codex:plugins/tailscale] Security

14/20

9 checks

[codex:plugins/tailscale] Operational Security

N/A

5 checks · not applicable

[codex:plugins/tailscale] Best Practices

9/15

5 checks

[codex:plugins/tailscale] Marketplace

N/A

3 checks · not applicable

[codex:plugins/tailscale] Skill Security

0/5

4 checks

[codex:plugins/tailscale] Code Quality

10/10

2 checks

Published advisories

None matched in OSV, checked . This covers published advisories only, not problems nobody has reported.

OSV is matched against the exact package versions this listing names.

Findings

highskill-securityRISKY_SKILL_INSTRUCTION

The skill includes "curl "https://api.tailscale.com/api/v2/tailnet/$TAILSCALE_TAILNET/devices" and uses curl with uploads, shell composition, or arguments requiring review.

Remove instructions that read sensitive local files, launch shell wrappers, or send workspace data to remote endpoints.

mediumsecurityCLAUDE_FIELD_MISSING_VERSION

The Claude manifest requires a non-empty "version" string.

Add "version" to the Claude manifest.

mediummanifest-validationPLUGIN_JSON_MISSING_VERSION

The manifest does not define a valid string for "version".

Add a non-empty string value for "version" in plugin.json.

lowsecuritySECURITY_MD_MISSINGReported 2 times

Plugins should publish a SECURITY.md file for responsible disclosure and support guidance.

Add a SECURITY.md file with reporting guidance and supported versions.

lowsecurityLICENSE_MISSINGReported 2 times

Plugins should ship a LICENSE file so consumers can review usage rights.

Add a LICENSE file that matches the manifest license metadata.

lowmanifest-validationPLUGIN_JSON_BAD_SEMVER

The version "" does not match the documented semver format.

Use a version like 1.2.3 in plugin.json.

lowbest-practicesREADME_MISSING

Plugins should document installation, usage, and security expectations in README.md.

Add a README.md that explains setup, usage, and operational constraints.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_PRIVACYPOLICYURL

The interface field "privacyPolicyURL" must use HTTPS or point to a safe in-repo asset.

Update "privacyPolicyURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_TERMSOFSERVICEURL

The interface field "termsOfServiceURL" must use HTTPS or point to a safe in-repo asset.

Update "termsOfServiceURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_COMPOSERICON

The interface field "composerIcon" must use HTTPS or point to a safe in-repo asset.

Update "composerIcon" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_LOGO

The interface field "logo" must use HTTPS or point to a safe in-repo asset.

Update "logo" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_SCREENSHOTS

The interface field "screenshots" must use HTTPS or point to a safe in-repo asset.

Update "screenshots" to use HTTPS or an existing relative asset path.

infobest-practicesCODEXIGNORE_MISSING

A .codexignore file helps prevent accidental inclusion of local artifacts and secrets.

Add a .codexignore file with generated assets, local state, and secret paths.

Install guidance

Install in MCP

Connect the bundled MCP server shipped in the repository .mcp.json file.

MCP docs
  1. 1

    Clone the repository

    shell
  2. 2

    Register the server in your MCP client

    Claude Code reads a project .mcp.json file and asks you to approve its servers when you open the folder. Other clients keep their own MCP configuration, so copy the server entry from .mcp.json into that client. If this repository configures its server differently, follow the MCP setup the publisher documents.

  3. 3

    Verify the server

    Check the MCP server list in your client. The server declared in .mcp.json should report as connected. In Claude Code, run /mcp to see it.

Did setup work in MCP?

No setup reports for MCP yet. Self-reported by signed-in visitors. Copying a command is not counted, and most installs are never reported.

Attested installs: Fewer than 10 attested installs of this plugin in week 2026-W43, so no number is shown. Counted from opt-in HOL Guard install reports, once per machine and runtime, and never mixed with the answers above. How install reports work.

Loading reviews

Plugin manifest

{
  "source": "official-mcp-registry",
  "evidenceState": "scanned_source",
  "registryName": "ai.dinglebear/tailscale-rmcp",
  "publishedAt": "2026-07-12T12:00:37.314618Z",
  "packages": [
    {
      "registryType": "npm",
      "identifier": "tailscale-rmcp",
      "version": "0.1.3",
      "transport": "stdio",
      "requiredEnvironment": [
        "TAILSCALE_API_KEY"
      ]
    }
  ],
  "remotes": [],
  "sourceScannedAt": "2026-10-30T15:41:53.302Z",
  "sourceScanCommit": "c8859f1efe3ecc964aa9fefbd58d5cea043715c8"
}

File inventory

File inventory is unavailable for this plugin right now.

Tailscale RMCP — Frequently asked questions

What is Tailscale RMCP?
Tailscale RMCP is an AI plugin in the HOL registry. Rust MCP server and CLI for Tailscale devices, users, keys, policies, and auth.
How do I install Tailscale RMCP?
Install Tailscale RMCP in your harness: MCP — git clone https://github.com/jmagar/tailscale-rmcp. Full step-by-step guidance is on the HOL plugin page.
How do I install Tailscale RMCP in MCP?
To install Tailscale RMCP in MCP, start with git clone https://github.com/jmagar/tailscale-rmcp. The complete step-by-step install guide for MCP is on the HOL plugin page.
Who publishes Tailscale RMCP?
Tailscale RMCP is published by ai.dinglebear and listed on HOL.

Directory acceptance

Listed in 0 of 5 directory lists

Read from the list each directory publishes on GitHub. Being listed means the directory accepted the plugin; it is not a HOL security rating.

Lists last read . HOL re-reads them every day.

Submitting it? Check it against each directory's rules

Install signal

HOL cannot see every install. These are separate signals from different sources, so they are not added together. Counts under each floor show as <N.

Install commands issued here
<5
HOL Guard install commands issued from this listing, last 28 days.
Opt-in install reports
<10
Machines that reported installing it through HOL Guard in week 2026-W43. Reporting is opt-in, so most installs are not counted.
HOL Guard workspaces
<5
Workspaces that approved it or include it in an approved-plugin feed, as of today.