Bitbucket (atlassian-dc-mcp) MCP Server

@atlassian-dc-mcp/bitbucket npm v0.34.0 Source verified

Published by b1ff — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Community-maintained MCP server for Atlassian Bitbucket Data Center. Not affiliated with Atlassian.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 25

Each tool and what it can reach — statically extracted from the published source.

  • bitbucket_createPullRequestingests untrusted input
  • bitbucket_canMergePullRequestno sensitive capability
  • bitbucket_createBranchno sensitive capability
  • bitbucket_getBranchDiffno sensitive capability
  • bitbucket_getCommitsno sensitive capability
  • bitbucket_getDashboardPullRequestsno sensitive capability
  • bitbucket_getFileContentno sensitive capability
  • bitbucket_getInboxPullRequestsno sensitive capability
  • bitbucket_getPR_CommentsAndActionno sensitive capability
  • bitbucket_getProjectno sensitive capability
Show 15 more tools ↓
  • bitbucket_getProjectsno sensitive capability
  • bitbucket_getPullRequestno sensitive capability
  • bitbucket_getPullRequestChangesno sensitive capability
  • bitbucket_getPullRequestDiffno sensitive capability
  • bitbucket_getPullRequestsno sensitive capability
  • bitbucket_getRepositoriesno sensitive capability
  • bitbucket_getRepositoryno sensitive capability
  • bitbucket_getRequiredReviewersno sensitive capability
  • bitbucket_getUserno sensitive capability
  • bitbucket_mergePullRequestno sensitive capability
  • bitbucket_postPullRequestCommentno sensitive capability
  • bitbucket_searchCodeno sensitive capability
  • bitbucket_submitPullRequestReviewno sensitive capability
  • bitbucket_updatePullRequestno sensitive capability
  • bitbucket_updatePullRequestCommentno sensitive capability

What this scan could not see

Versions 5

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.34.0 latest A 97/100 0 1.13.0 2026-09-07
v0.33.0 A 97/100 0 1.13.0 2026-09-01
v0.29.0 A 97/100 0 1.13.0 2026-08-30
v0.28.0 A 97/100 0 1.10.0 2026-07-25
v0.27.0 A 100/100 0 1.5.0 2026-07-22

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/atlassian-dc-mcp-bitbucket/badge.svg)](https://mcptrustchecker.com/registry/atlassian-dc-mcp-bitbucket)
HTML
<a href="https://mcptrustchecker.com/registry/atlassian-dc-mcp-bitbucket"><img src="https://mcptrustchecker.com/registry/atlassian-dc-mcp-bitbucket/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/atlassian-dc-mcp-bitbucket/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @atlassian-dc-mcp/bitbucket --online

Use the free API → How scoring works

Other implementations of Bitbucket 24

Independent packages implementing the same tool, scanned with the same engine. Compare all 25 side by side →

More in Data Science & ML