Back to MCP Trust Indexm8ven
65
/ 100
1 month ago
npm

bitbucket-mcp

Model Context Protocol (MCP) server for Bitbucket Cloud and Server API integration

→ MatanYemini/bitbucket-mcp· npm: bitbucket-mcp· listed on npm
Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

npmmcp.soGitHub

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Known vulnerabilities in dependencies: 16 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: BITBUCKET_PASSWORD, BITBUCKET_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies16 high1 medium12 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.1.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.1.1GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highaxios@1.6.5GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.6.5GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.6.5GHSA-43fc-jf86-j433

Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configBITBUCKET_ALLOW_DANGEROUS
configBITBUCKET_ENABLE_DANGEROUS— Set to true to enable dangerous tools (e.g., deletions). Default: disabled No
configBITBUCKET_LOG_DIR— Directory to store logs (defaults to OS-specific app log dir) No
configBITBUCKET_LOG_DISABLE— Disable file logging when set to true/1 No
configBITBUCKET_LOG_FILE— Absolute path to a specific log file No
configBITBUCKET_LOG_PER_CWD— When true, nest logs under a per-working-directory subfolder No
🔐 secretBITBUCKET_PASSWORD— "your-app-password" \
🔐 secretBITBUCKET_TOKEN— Your Bitbucket access token (alternative to username/password) No
configBITBUCKET_URL— "https://api.bitbucket.org/2.0" \
configBITBUCKET_USERNAME— Since it has been asked, in many cases we have seen - "" is usually your email
configBITBUCKET_WORKSPACE— "your-workspace" \
configXDG_STATE_HOME
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 1 concrete improvement we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/bitbucket-mcp-wyp11p)](https://m8ven.ai/mcp/bitbucket-mcp-wyp11p)
commit: d3594e2cfaae879ae2aa2ef15b0139c0aa6dc0f6
code hash: 4a9336c6410adc5f62dc0e1b5a05ba93ed8c4ecc5151dcfc17ad2ee578c92573
verified: 6/16/2026, 12:59:43 PM
view raw JSON →