Skills/PyPI/troubleshoot-mcp-server

troubleshoot-mcp-server@1.15.1

VERIFIED· not started

Publisher claims: "MCP server for Kubernetes support bundles" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher chrisns · publishing for 402 daysInstalls 90Last detonated 1 h ago
$claude mcp add troubleshoot-mcp-server -- uvx troubleshoot-mcp-server
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
GITHUB_TOKENMCP_TOKEN_LIMITSBCTL_TOKENConfiguration, not credentials: CLEANUP_INTERVAL, ENABLE_LIST_BUNDLES_TOOL, ENABLE_PERIODIC_CLEANUP, MAX_DOWNLOAD_SIZE, MAX_DOWNLOAD_TIMEOUT, MAX_INITIALIZATION_TIMEOUT, MCP_BUNDLE_STORAGE, MCP_CONFIG_PATH, MCP_DEBUG, MCP_LOG_LEVEL, MCP_SINGLE_BUNDLE_MODE, MCP_SIZE_CHECK_ENABLED, MCP_USE_STDIO, MCP_VERBOSITY, MOCK_K8S_API_PORT, PRESERVE_BUNDLES, REPLICATED, SBCTL_ALLOW_ALTERNATIVE_KUBECONFIG, SBCTL_CLEANUP_ORPHANED
Where it talks to
no vendor host named in the codeAlso replicated.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 replicated.com as well as its own vendor. The guard injects GITHUB_TOKEN, MCP_TOKEN_LIMIT, SBCTL_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx troubleshoot-mcp-server

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-20 and scored it 89/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

MEDIUM
MCP server using network transport (SSE/HTTP)pyproject.toml:23 · MCP server using network transport (SSE/HTTP) — data sent over network… "debugging", ] urls = { "Homepage" = "https://github.com/chrisns/troubleshoot-mcp-server", "Repository" = "https://github.com/chrisns/troubleshoot-mcp-server", "Issues" = "https://github.com/chrisns/troubleshoot-mcp-server/issues" } requi…Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
Process kill commandsrc/troubleshoot_mcp_server/bundle.py:1769 · Process kill command — agent can terminate processes# Try to kill the process if it existsFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Process kill commandsrc/troubleshoot_mcp_server/bundle.py:1786 · Process kill command — agent can terminate processeslogger.warning(f"Permission error trying to kill process {pid}")Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Process kill commandsrc/troubleshoot_mcp_server/bundle.py:1809 · Process kill command — agent can terminate processes# Use psutil to find and kill sbctl processes using our bundleFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05

Cost to the agent

Instructions loaded
≈53 tok
1 file · 25 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

Not checked against OSV yet; the weekly check has not reached this version.