Bitbucket Server (upendra_sengar) MCP Server

@upendra_sengar/bitbucket-server-mcp npm v0.1.0

Published by @upendra_sengar — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Bitbucket Server / Data Center with code review, cross-repo PRs, and CI insights

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/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
High
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 = 93/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 − 7 = 93. 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
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 5

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: browse_repository → get_file_content → create_pull_request. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow browse_repository → get_file_content → create_pull_request

medium Tool "edit_file" can modify the filesystemMTC-CAP-002

Tool "edit_file" can write, overwrite or delete files (keyword "edit_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool edit_file

low Mutating tool "edit_file" declares no destructiveHintMTC-CAP-005

Tool "edit_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool edit_file

low Unconstrained path parameter "filePath" on "get_file_content"MTC-CAP-008

Tool "get_file_content" takes a path parameter "filePath" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool get_file_content · inputSchema.properties.filePath

low Unconstrained path parameter "filePath" on "edit_file"MTC-CAP-008

Tool "edit_file" takes a path parameter "filePath" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool edit_file · inputSchema.properties.filePath

Tools 59

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

  • browse_repositoryingests untrusted input
  • create_pull_requestnetwork egress
  • edit_filewrites files
  • get_file_contentreads sensitive data
  • compare_refsno sensitive capability
  • create_repositoryno sensitive capability
  • decline_pull_requestno sensitive capability
  • delete_repositoryno sensitive capability
  • fork_repositoryno sensitive capability
  • get_build_statusno sensitive capability
Show 49 more tools ↓
  • get_code_insightsno sensitive capability
  • get_commitno sensitive capability
  • get_commit_pull_requestsno sensitive capability
  • get_diffno sensitive capability
  • get_file_blameno sensitive capability
  • get_pull_requestno sensitive capability
  • get_pull_request_activityno sensitive capability
  • get_pull_request_commitsno sensitive capability
  • get_server_infono sensitive capability
  • get_tagno sensitive capability
  • get_user_profileno sensitive capability
  • list_branch_restrictionsno sensitive capability
  • list_branchesno sensitive capability
  • list_commit_commentsno sensitive capability
  • list_commitsno sensitive capability
  • list_dashboard_pull_requestsno sensitive capability
  • list_default_reviewer_conditionsno sensitive capability
  • list_forksno sensitive capability
  • list_gpg_keysno sensitive capability
  • list_labelsno sensitive capability
  • list_merge_checksno sensitive capability
  • list_projectsno sensitive capability
  • list_pull_requestsno sensitive capability
  • list_repositoriesno sensitive capability
  • list_repository_hooksno sensitive capability
  • list_reviewer_groupsno sensitive capability
  • list_secret_scanning_rulesno sensitive capability
  • list_ssh_keysno sensitive capability
  • list_tagsno sensitive capability
  • list_webhooksno sensitive capability
  • manage_branchesno sensitive capability
  • manage_commentno sensitive capability
  • manage_commit_commentsno sensitive capability
  • manage_deploymentsno sensitive capability
  • manage_gpg_keysno sensitive capability
  • manage_labelsno sensitive capability
  • manage_merge_checksno sensitive capability
  • manage_repository_hooksno sensitive capability
  • manage_reviewno sensitive capability
  • manage_reviewer_groupsno sensitive capability
  • manage_ssh_keysno sensitive capability
  • manage_tagsno sensitive capability
  • manage_webhooksno sensitive capability
  • merge_pull_requestno sensitive capability
  • searchno sensitive capability
  • search_emoticonsno sensitive capability
  • search_usersno sensitive capability
  • update_pull_requestno sensitive capability
  • upload_attachmentno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

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.1.0 latest A 93/100 5 1.13.0 2026-09-07

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 · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/upendra-sengar-bitbucket-server-mcp/badge.svg)](https://mcptrustchecker.com/registry/upendra-sengar-bitbucket-server-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/upendra-sengar-bitbucket-server-mcp"><img src="https://mcptrustchecker.com/registry/upendra-sengar-bitbucket-server-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/upendra-sengar-bitbucket-server-mcp/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 @upendra_sengar/bitbucket-server-mcp --online

Use the free API → How scoring works

Other implementations of Bitbucket Server 24

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

More in Developer Tools