Skills/PyPI/spaceship-mcp

spaceship-mcp@0.1.6

VERIFIED· not started

Publisher claims: "MCP server for Spaceship AI — manage agents from Claude Code and other MCP clients" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher spaceship-ai · publishing for 237 daysInstalls 55Last detonated 1 h ago
$claude mcp add spaceship-mcp -- uvx spaceship-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
SPACESHIP_API_KEYConfiguration, not credentials: SPACESHIP_API_URL
Where it talks to
spaceshipai.io (its own)
What the honeypot saw
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. It asks for SPACESHIP_API_KEY and talks to spaceshipai.io. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets SPACESHIP_API_KEY=spaceshipai.io -- uvx spaceship-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-18 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

MEDIUM
npx invocation of non-well-known packagetests/test_projects.py:46 · npx invocation of non-well-known package — may execute untrusted codeassert "npx spaceshipai@latest init" in str(exc_info.value)Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagesrc/spaceship_mcp/client.py:63 · npx invocation of non-well-known package — may execute untrusted code"Run `npx spaceshipai@latest init` to re-authenticate.",Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈57 tok
1 file · 18 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 spaceship-mcp@0.1.6 as of 36 min ago. This is the package itself, not its dependencies.