Skills/npm/bitbucket-dc-mcp

bitbucket-dc-mcp@1.9.1

VERIFIED· startup only

Publisher claims: "HTTP MCP server for Bitbucket Data Center REST API" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher shibainu16 · publishing for 284 daysInstalls 11,835Last detonated 1 h ago
$claude mcp add bitbucket-dc-mcp -- npx -y @shibainu16/bitbucket-dc-mcp
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

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
BITBUCKET_PASSWORDBITBUCKET_TOKENMCP_AUTH_TOKENConfiguration, not credentials: BITBUCKET_DEFAULT_PROJECT, BITBUCKET_ENABLE_DANGEROUS, BITBUCKET_MAX_CHARS, BITBUCKET_TIMEOUT_MS, BITBUCKET_URL, BITBUCKET_USERNAME, BITBUCKET_VERBOSE, CORS_ORIGIN, MCP_MAX_SESSIONS, MCP_SESSION_IDLE_TTL_MS, MCP_TRANSPORT
Where it talks to
no vendor host named in the code
What we saw when it ran
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it with a scoped credential, under the guard. It asks for BITBUCKET_PASSWORD, BITBUCKET_TOKEN, MCP_AUTH_TOKEN and talks to its vendor. 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 --net declared -- npx -y @shibainu16/bitbucket-dc-mcp

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

What changed since 1.7.0

vet-skills diff bitbucket-dc-mcp 1.7.0 1.9.1

In the sandbox, this version reached for nothing 1.7.0 did not. Compared from the two recorded runs, not from source.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-21 and scored it 90/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 · 28 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
8.0sprocessdependency install exit 0
28sclaimedstartup only: exited (0) before answering · at process.processTicksAndRejections (node:internal/process/task_queues:103:5) at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:681:26) at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:117:5) ◇ injected env (0) from .env // tip: ⌘ multiple files { path: ['.env.local', '.env'] }
28sprocessscript backend runs setup only
28sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsbuild/server/boot.js:9 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// Load environment variables from .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
File permission modification commandpackage.json:13 · File permission modification command — agent changes file ownership/permissions"build": "tsc && chmod 755 build/index.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

Cost to the agent

Instructions loaded
≈53 tok
1 file · 37 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 @shibainu16/bitbucket-dc-mcp@1.9.1 as of 37 min ago. This is the package itself, not its dependencies.