Skills/PyPI/tailscale-blade-mcp

tailscale-blade-mcp@0.9.0

VERIFIED· not started

Publisher claims: "MCP server for Tailscale network monitoring and security — devices, ACLs, DNS, keys, users, audit logs" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher groupthink-dev · publishing for 206 daysInstalls 65Last detonated 16 h ago
$claude mcp add tailscale-blade-mcp -- uvx tailscale-blade-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
TAILSCALE_API_KEYTAILSCALE_MCP_API_TOKENConfiguration, not credentials: STALLARI_STATE_ROOT, TAILSCALE_API_BASE, TAILSCALE_LOG_LEVEL, TAILSCALE_MCP_HOST, TAILSCALE_MCP_PORT, TAILSCALE_MCP_TRANSPORT, TAILSCALE_TAILNET, TAILSCALE_WRITE_ENABLED
Where it talks to
no vendor host named in the codeAlso tailscale.com — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names tailscale.com as well as its own vendor. The guard injects TAILSCALE_API_KEY, TAILSCALE_MCP_API_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx tailscale-blade-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-19 and scored it 91/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

HIGH
Auto-update or dynamic fetch configurationsrc/tailscale_blade_mcp/formatters.py:146 · Auto-update or dynamic fetch configuration — agent may load new code at runtimeif s.get("devicesAutoUpdatesOn"):Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
Auto-update or dynamic fetch configurationtests/conftest.py:97 · Auto-update or dynamic fetch configuration — agent may load new code at runtime"devicesAutoUpdatesOn": True,Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈647 tok
2 files · 30 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for tailscale-blade-mcp@0.9.0 as of 16 h ago. This is the package itself, not its dependencies.

tailscale-blade-mcp@0.9.0 safety verdict: Verified (not started) — KillerSkills