Skills/PyPI/spacebridge-mcp

spacebridge-mcp@0.3.0

VERIFIED· not started

Publisher claims: "SpaceBridge MCP Server for issue tracker automation." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher spacecode-ai · publishing for 577 daysInstalls 54Last detonated 1 h ago
$claude mcp add spacebridge-mcp -- uvx spacebridge-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
OPENAI_API_KEYSPACEBRIDGE_API_KEY or --spacebridge-api-key / --openai-api-keyConfiguration, not credentials: DUPLICATE_SIMILARITY_THRESHOLD, OPENAI_API_BASE, OPENAI_MODEL, SPACEBRIDGE_API_URL, SPACEBRIDGE_ORG_NAME, SPACEBRIDGE_PROJECT_NAME
Where it talks to
spacebridge.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 OPENAI_API_KEY, SPACEBRIDGE_API_KEY and talks to spacebridge.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 OPENAI_API_KEY=spacebridge.io,SPACEBRIDGE_API_KEY=spacebridge.io -- uvx spacebridge-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 86/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
Access to sensitive file pathssrc/spacebridge_mcp/server.py:44 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Configuration will be loaded in main_sync using argparse, environment variables, and .env file.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/spacebridge_mcp/server.py:45 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Precedence: Command-line args > Environment variables > .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/spacebridge_mcp/server.py:13 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesfrom dotenv import load_dotenv # Added for .env supportFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/spacebridge_mcp/server.py:50 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesGets a configuration value based on precedence: command-line args, environment variables, .env file.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathspyproject.toml:27 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"python-dotenv>=0.19.0", # For loading .env filesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/spacebridge_mcp/server.py:60 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Environment variable (which might have been loaded from .env)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_server.py:699 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesmock_os_path_exists.return_value = True # Assume .env exists but is ignoredFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

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