Tailscale MCP
NPM · @TMHS/TAILSCALE-MCP
Let AI agents see and use your tailnet: status, SSH config, Serve/Funnel sharing, ping matrix
Available components
Last scanned (21 hours ago)
Scores higher than 72% of npm servers
Category Cloud Infrastructure
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency87
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to TMHSDigital/tailscale-mcp). View diagnostics → Pass
- License check failed: the license (CC-BY-NC-ND-4.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 9 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@tmhs/tailscale-mcp@0.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | TMHSDigital/tailscale-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/TMHSDigital/tailscale-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3471536070 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1b0758bbb3b2dad91c1d22cd1c54b3fb66a49274021f99296db1938cd622dcf0005e1f4e2fdc62fb6073c96f3332f7f4049dfc11fa086230ab58affd6 |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
generate_ssh_config Generate SSH config ~236
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| backup | string|null | – | – |
| configText | string | – | Generated config (dry run) |
| dryRun | boolean | yes | – |
| hostCount | number | yes | – |
| instructions | string | – | – |
| note | string | – | – |
| renamed | array | – | – |
| skipped | array | – | – |
| wrote | string|null | – | File written; null when nothing changed |
No examples provided.
ping_all Ping all peers ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| matrix | array | yes | – |
| pinged | number | yes | – |
| reachable | number | yes | – |
| timedOut | boolean | yes | – |
No examples provided.
share_port Share a local port ~191
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).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | HTTPS mount path on the serve endpoint, e.g. "/api" (default: "/") |
| port | integer | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| port | number | yes | – |
| public | boolean | yes | – |
| scope | string | yes | – |
| urls | array | yes | – |
No examples provided.
share_status Share status ~65
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | yes | – |
| endpoints | array | yes | – |
| publicExposure | boolean|null | yes | 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 | – | – |
No examples provided.
stop_share Stop sharing ~224
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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: "/") |
| Name | Type | Req | Description |
|---|---|---|---|
| failures | array | – | – |
| remaining | object | yes | – |
| removed | array | yes | – |
| stopped | – | yes | – |
No examples provided.
tailnet_status Tailnet status ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| onlineOnly | boolean | – | Only include peers that are currently online (default: false) |
| Name | Type | Req | Description |
|---|---|---|---|
| backendState | string | yes | – |
| health | array | yes | – |
| magicDNSSuffix | string | yes | – |
| peerCount | number | yes | Total peers, before any onlineOnly filter |
| peers | array | yes | – |
| self | object | yes | – |
| tailnet | string | yes | – |
No examples provided.
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.
npm · @tmhs/tailscale-mcp
claude mcp add tmhsdigital-tailscale-mcp -- npx -y @tmhs/tailscale-mcp
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 4 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 4 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.