Skills/PyPI/shipboss-mcp-server

shipboss-mcp-server@4.0.12

VERIFIED· not started

Publisher claims: "ShipBoss MCP server with parcel & freight endpoints" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher shipboss-support · publishing for 451 daysInstalls 71Last detonated 2 h ago
$claude mcp add shipboss-mcp-server -- uvx shipboss-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
SHIPBOSS_API_TOKEN or --api-token
Where it talks to
shipboss.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 SHIPBOSS_API_TOKEN and talks to shipboss.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 SHIPBOSS_API_TOKEN=shipboss.io -- uvx shipboss-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-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 pathsshipboss_mcp_server.py:23 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Load .env file from the script's directoryFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsshipboss_mcp_server.py:22 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Get API token from command-line arguments, environment variables, or .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 pathsshipboss_mcp_server.py:45 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filessource = "command-line argument" if args.api_token else "environment/.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 pathsshipboss_mcp_server.py:25 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv_file = os.path.join(script_dir, '.env')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 pathsshipboss_mcp_server.py:39 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files" 1. Create a .env file with SHIPBOSS_API_TOKEN=your_token\n"Fix: 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
≈53 tok
1 file · 12 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 shipboss-mcp-server@4.0.12 as of 1 h ago. This is the package itself, not its dependencies.