Tailscale Compute
NPM · @DYLANTIRANDAZ/TAILSCALE-COMPUTE-MCP
Run builds, tests, and benchmarks on your own Tailscale compute node.
Available components
Last scanned (3 hours ago)
Scores higher than 89% of npm servers
Category Testing and QA
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 Security100
- 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
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 63 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 303 tokens (~151/item across 2 items; 2 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 Management97
- Stability observed for 29 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 12 Oct 26 −3
- Stability: pass → 0.80 functional
- 11 Oct 26 +2
- Stability: 0.83 → pass security
- Security disclosure: pass → unverified ▼ functional
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 83. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 −3
- Stability: pass → 0.77 functional
- 3 Oct 26 0
- Stability: 0.97 → pass security
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 17 Oct 2026 · Analysed npm/@dylantirandaz/tailscale-compute-mcp@0.1.0-beta.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| 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 →
compute_run Run on Tailscale Compute ~231
Sync the local project and run one non-interactive command on the configured Tailscale compute node. Use it for builds, tests, benchmarks, and other costly work. Keep file edits local. The command has the full permissions of the remote SSH user.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | array | – | The exact arguments for the remote program. |
| environment | object | – | Environment variables for this command only. |
| program | string | yes | The executable name or path. For shell syntax, use a shell available on the remote node with arguments such as ['-lc', 'your command']. |
| standardInput | string | – | Optional UTF-8 input for the remote program. |
| syncMode | string | – | Use incremental for normal runs, clean to replace the remote workspace, or none to reuse the last remote snapshot. |
| timeoutSeconds | integer | – | The maximum time for each sync or command process. |
| workingDirectory | string | – | A POSIX path relative to the remote workspace. |
| workspacePath | string | – | The absolute local project path. Omit it when the MCP host starts this server in the project directory. |
Structured output declared, but exposes no named fields.
No examples provided.
compute_status Check Tailscale Compute ~72
Check the configured Tailscale compute node and report its operating system, hardware, remote shell, and accelerator inventory. Use this before the first remote run or after a connection failure.
| Name | Type | Req | Description |
|---|---|---|---|
| workspacePath | string | – | The absolute local project path. Omit it when the MCP host starts this server in the project directory. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Tailscale Compute MCP server?
Tailscale Compute runs locally as an npm package, launched with npx -y @dylantirandaz/tailscale-compute-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 · @dylantirandaz/tailscale-compute-mcp
claude mcp add dylantirandaz-tailscale-compute -- npx -y @dylantirandaz/tailscale-compute-mcp
What is the Tailscale Compute MCP server?
Tailscale Compute is an MCP server listed in the public MCP registry as io.github.dylantirandaz/tailscale-compute. Run builds, tests, and benchmarks on your own Tailscale compute node. This page covers its npm package (@dylantirandaz/tailscale-compute-mcp).
Is the Tailscale Compute MCP server safe to use?
Tailscale Compute scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. 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 Compute MCP server expose?
Tailscale Compute exposes 2 tools: compute_status, compute_run. Their descriptions and schemas cost roughly 303 tokens of context every time the server is loaded.
Is the Tailscale Compute MCP server still maintained?
Tailscale Compute is still listed as active in the MCP registry. We last reached this channel on 17 October 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 Compute MCP server under?
Tailscale Compute declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.