Tailscale Compute
NPM · @DYLANTIRANDAZ/TAILSCALE-COMPUTE-MCP · SCANNED AUG 17
Run builds, tests, and benchmarks on your own Tailscale compute node.
Available components
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 →
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 2 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @dylantirandaz/tailscale-compute-mcp
claude mcp add dylantirandaz-tailscale-compute -- npx -y @dylantirandaz/tailscale-compute-mcp
codex mcp add dylantirandaz-tailscale-compute -- npx -y @dylantirandaz/tailscale-compute-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dylantirandaz-tailscale-compute": {
"type": "local",
"command": [
"npx",
"-y",
"@dylantirandaz/tailscale-compute-mcp"
],
"enabled": true
}
}
} openclaw mcp add dylantirandaz-tailscale-compute --command npx --arg -y --arg @dylantirandaz/tailscale-compute-mcp
mcp_servers:
dylantirandaz-tailscale-compute:
command: "npx"
args: ["-y", "@dylantirandaz/tailscale-compute-mcp"] {
"mcpServers": {
"dylantirandaz-tailscale-compute": {
"command": "npx",
"args": [
"-y",
"@dylantirandaz/tailscale-compute-mcp"
]
}
}
} 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.
- 15 Aug 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- 13 Aug 26 60
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 17 Aug 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 |
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| Tree resolution | Complete |
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.
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.