# Tailscale MCP (npm · @tmhs/tailscale-mcp)

Let AI agents see and use your tailnet: status, SSH config, Serve/Funnel sharing, ping matrix

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@tmhs/tailscale-mcp`: 82/100 (this document), [markdown](https://verifymcp.io/servers/tmhsdigital-tailscale-mcp/tmhs-tailscale-mcp.md), [page](https://verifymcp.io/servers/tmhsdigital-tailscale-mcp/tmhs-tailscale-mcp)

## Channel facts

- Registry: `npm`
- Package: `@tmhs/tailscale-mcp`
- Version: `0.4.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 87/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to TMHSDigital/tailscale-mcp).
  - License check failed: the license (CC-BY-NC-ND-4.0) isn't a recognized OSI-approved license.
  - Actively maintained (last published 10 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 961 tokens (~160/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Tailscale MCP server?

Tailscale MCP runs locally as an npm package, launched with npx -y @tmhs/tailscale-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add tmhsdigital-tailscale-mcp -- npx -y @tmhs/tailscale-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "tmhsdigital-tailscale-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tmhs/tailscale-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tmhsdigital-tailscale-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tmhs/tailscale-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add tmhsdigital-tailscale-mcp -- npx -y @tmhs/tailscale-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tmhsdigital-tailscale-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@tmhs/tailscale-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tmhsdigital-tailscale-mcp --command npx --arg -y --arg @tmhs/tailscale-mcp
```

### Hermes

```yaml
mcp_servers:
  tmhsdigital-tailscale-mcp:
    command: "npx"
    args: ["-y", "@tmhs/tailscale-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "tmhsdigital-tailscale-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@tmhs/tailscale-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add tmhsdigital-tailscale-mcp -t stdio -c npx -a -y @tmhs/tailscale-mcp
```

### Other

```json
{
  "mcpServers": {
    "tmhsdigital-tailscale-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tmhs/tailscale-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 78)

First indexed and scored.

## MCP tools (6)

### `tailnet_status` (~101 tokens)

Tailnet status

Report the state of the local tailnet: this node plus all peers with hostname, MagicDNS name, Tailscale IPv4/IPv6, OS, online flag, last seen, exit-node flags, and tags. Returns a structured error with the exact fix command when the tailscale binary is missing, the daemon is stopped, or the device needs login.

Input parameters:

- `onlineOnly` (boolean): Only include peers that are currently online (default: false)

Output parameters:

- `backendState` (string)
- `health` (array)
- `magicDNSSuffix` (string)
- `peerCount` (number): Total peers, before any onlineOnly filter
- `peers` (array)
- `self` (object)
- `tailnet` (string)

### `generate_ssh_config` (~236 tokens)

Generate SSH config

Generate ssh-config Host blocks for tailnet nodes (MagicDNS name preferred, Tailscale IP fallback). Dry-run by default: returns the generated config text only and writes nothing. With write=true it writes a dedicated file (~/.ssh/tailscale_dev_config) and returns instructions for adding an Include line to ~/.ssh/config (never applied automatically). Direct editing of ~/.ssh/config itself additionally requires target="user_ssh_config" and is idempotent between managed markers, never touching content outside them.

Input parameters:

- `includeShared` (boolean): Include nodes of users this node is shared with (default: false). Mullvad exit nodes are always skipped.
- `onlineOnly` (boolean): Only include peers that are currently online (default: false)
- `target` (string): Write target: "dedicated_file" (default, ~/.ssh/tailscale_dev_config) or "user_ssh_config" (edit ~/.ssh/config between managed markers)
- `user` (string): Remote user to set on every Host block
- `write` (boolean): Actually write the config (default: false = dry-run, text only)

Output parameters:

- `backup` (string|null)
- `configText` (string): Generated config (dry run)
- `dryRun` (boolean)
- `hostCount` (number)
- `instructions` (string)
- `note` (string)
- `renamed` (array)
- `skipped` (array)
- `wrote` (string|null): File written; null when nothing changed

### `share_status` (~65 tokens)

Share status

Report the active Tailscale Serve/Funnel sessions on this node: one entry per endpoint with its URL, serve port, mount path, proxied target, and a public flag that is true when Funnel exposes it to the open internet. publicExposure is true when anything is public.

Output parameters:

- `active` (boolean)
- `endpoints` (array)
- `publicExposure` (boolean|null): True when any endpoint is exposed via Funnel; null if unknown (old CLI)
- `status` (string): Raw text status, only on CLIs without --json
- `tcpForwards` (array)

### `share_port` (~191 tokens)

Share a local port

Share a local port over the tailnet via Tailscale Serve (tailnet-only by default). WARNING: setting public=true switches to Funnel and exposes the port to the OPEN INTERNET — anyone with the URL can reach it. Only set public=true when internet exposure is explicitly intended. Funnel is DISABLED on this server: public=true returns FUNNEL_DISABLED unless the user sets TAILSCALE_MCP_ALLOW_FUNNEL=1. Returns the resulting URL(s).

Input parameters:

- `path` (string): HTTPS mount path on the serve endpoint, e.g. "/api" (default: "/")
- `port` (integer, required): Local port to share
- `public` (boolean): Expose to the open internet via Funnel (default: false = tailnet-only Serve). DANGEROUS: public=true makes the port reachable by anyone on the internet. Disabled unless TAILSCALE_MCP_ALLOW_FUNNEL=1.

Output parameters:

- `port` (number)
- `public` (boolean)
- `scope` (string)
- `urls` (array)

### `stop_share` (~224 tokens)

Stop sharing

Stop Serve/Funnel shares: one mount, the shares this server created, or all of them, reporting what was removed. Name exactly one target: httpsPort and/or path turns off that one mount (httpsPort is the serve port shown in share_status, typically 443, not the proxied local port; path is the mount path given to share_port, default "/"); mine=true stops only the shares this server created in this session; all=true clears the entire serve/funnel configuration, including shares set up outside this server. With no arguments nothing is stopped and the active endpoints are listed. Returns what was removed and what remains.

Input parameters:

- `all` (boolean): Clear the ENTIRE serve/funnel config, including shares not created by this server
- `httpsPort` (integer): HTTPS serve port of the mount to turn off (default 443 when path is given)
- `mine` (boolean): Stop only the shares created by share_port in this session
- `path` (string): Mount path to turn off, as passed to share_port (default: "/")

Output parameters:

- `failures` (array)
- `remaining` (object)
- `removed` (array)
- `stopped`

### `ping_all` (~144 tokens)

Ping all peers

Ping tailnet peers concurrently (bounded to 5 at a time, with a per-ping timeout) and return a latency matrix: node, latency ms of the settled path, path (direct, DERP relay, or peer relay), or unreachable. Defaults to online peers only. The whole call is capped at 45s; peers not answered by then are reported with an error and timedOut is true.

Input parameters:

- `count` (integer): Ping attempts per peer (default: 1)
- `onlineOnly` (boolean): Only ping peers reported online (default: true)
- `timeoutMs` (integer): Per-ping timeout in milliseconds (default: 5000)

Output parameters:

- `matrix` (array)
- `pinged` (number)
- `reachable` (number)
- `timedOut` (boolean)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/tmhsdigital-tailscale-mcp/tmhs-tailscale-mcp#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79
- 2026-10-28: 79
- 2026-10-27: 78
- 2026-10-26: 78

## Common questions

### What is the Tailscale MCP server?

Tailscale MCP is listed in the public MCP registry as io.github.TMHSDigital/tailscale-mcp. Let AI agents see and use your tailnet: status, SSH config, Serve/Funnel sharing, ping matrix. This page covers its npm package (@tmhs/tailscale-mcp).

### Is the Tailscale MCP server safe to use?

Tailscale MCP scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Tailscale MCP server expose?

Tailscale MCP exposes 6 tools: tailnet_status, generate_ssh_config, share_status, share_port, stop_share, ping_all. Their descriptions and schemas cost roughly 961 tokens of context every time the server is loaded.

### Is the Tailscale MCP server still maintained?

Tailscale MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Tailscale MCP server under?

Tailscale MCP declares the CC-BY-NC-ND-4.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@tmhs/tailscale-mcp
- Socket report: https://socket.dev/npm/package/@tmhs/tailscale-mcp
- Repository: https://github.com/TMHSDigital/tailscale-mcp
- Website: https://tmhsdigital.github.io/tailscale-mcp/
- Changelog RSS feed: https://verifymcp.io/servers/tmhsdigital-tailscale-mcp/tmhs-tailscale-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tmhsdigital-tailscale-mcp/tmhs-tailscale-mcp.json
- HTML version of this page: https://verifymcp.io/servers/tmhsdigital-tailscale-mcp/tmhs-tailscale-mcp