Bitbucket (PyPI) MCP Server
bitbucket-mcp
PyPI
v0.5.0
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP server for comprehensive Bitbucket Cloud API integration
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 − 8 = 92. 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:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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 1
high Sensitive-source and external-sink co-existMTC-FLOW-004
Tools that read sensitive data ([get_file_contents]) and tools that can send data out ([create_issue, create_pull_request, create_webhook, delete_webhook]) are exposed together. An agent can move private data to the sink.
Evidence: sources [get_file_contents] → sinks [create_issue, create_pull_request, create_webhook, delete_webhook]
Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.
Location: flow get_file_contents → create_issue
Tools 79
Each tool and what it can reach — statically extracted from the published source.
create_issuenetwork egresscreate_pull_requestnetwork egresscreate_webhooknetwork egressdelete_webhooknetwork egressget_file_contentsreads sensitive dataadd_inline_commentno sensitive capabilityadd_issue_commentno sensitive capabilityadd_pull_request_commentno sensitive capabilityadd_reviewerno sensitive capabilityapprove_pull_requestno sensitive capability
Show 69 more tools ↓
create_branchno sensitive capabilitycreate_build_statusno sensitive capabilitycreate_pipeline_variableno sensitive capabilitycreate_projectno sensitive capabilitycreate_repositoryno sensitive capabilitycreate_snippetno sensitive capabilitycreate_tagno sensitive capabilitydecline_pull_requestno sensitive capabilitydelete_branchno sensitive capabilitydelete_commentno sensitive capabilitydelete_repositoryno sensitive capabilitydelete_snippetno sensitive capabilitydelete_tagno sensitive capabilityfork_repositoryno sensitive capabilityget_branching_modelno sensitive capabilityget_commitno sensitive capabilityget_commit_diffno sensitive capabilityget_commit_diffstatno sensitive capabilityget_config_statusno sensitive capabilityget_current_userno sensitive capabilityget_default_reviewersno sensitive capabilityget_issueno sensitive capabilityget_pipelineno sensitive capabilityget_pipeline_step_logno sensitive capabilityget_projectno sensitive capabilityget_pull_requestno sensitive capabilityget_pull_request_activityno sensitive capabilityget_pull_request_commentsno sensitive capabilityget_pull_request_commitsno sensitive capabilityget_pull_request_diffno sensitive capabilityget_pull_request_diffstatno sensitive capabilityget_pull_request_merge_statusno sensitive capabilityget_repositoryno sensitive capabilityget_snippetno sensitive capabilityget_user_permissionsno sensitive capabilityget_user_profileno sensitive capabilityget_workspace_detailsno sensitive capabilitylist_branchesno sensitive capabilitylist_commit_commentsno sensitive capabilitylist_commit_statusesno sensitive capabilitylist_commitsno sensitive capabilitylist_issue_commentsno sensitive capabilitylist_issuesno sensitive capabilitylist_pipeline_stepsno sensitive capabilitylist_pipeline_variablesno sensitive capabilitylist_pipelinesno sensitive capabilitylist_projectsno sensitive capabilitylist_pull_requestsno sensitive capabilitylist_repositoriesno sensitive capabilitylist_repository_forksno sensitive capabilitylist_snippetsno sensitive capabilitylist_tagsno sensitive capabilitylist_webhooksno sensitive capabilitylist_workspace_membersno sensitive capabilitylist_workspace_permissionsno sensitive capabilitylist_workspace_webhooksno sensitive capabilitylist_workspacesno sensitive capabilitymerge_pull_requestno sensitive capabilityremove_reviewerno sensitive capabilityreply_to_commentno sensitive capabilityrequest_changes_pull_requestno sensitive capabilitysearch_codeno sensitive capabilitysetup_bitbucketno sensitive capabilitystop_pipelineno sensitive capabilitytrigger_pipelineno sensitive capabilityunapprove_pull_requestno sensitive capabilityupdate_issueno sensitive capabilityupdate_pull_requestno sensitive capabilityupdate_repositoryno 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
- Tools were statically extracted from the published source (79 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.5.0 latest |
A 92/100 | 1 | 1.13.0 | 2026-08-25 |
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.
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 bitbucket-mcp --online --registry pypiOther implementations of Bitbucket 24
Independent packages implementing the same tool, scanned with the same engine. Compare all 25 side by side →
MCP server for Bitbucket — manage pull requests, branches, and repositories from any MCP client
Model Context Protocol (MCP) server for Bitbucket Cloud and Server API integration
MCP server for Bitbucket Cloud — read and manage pull requests, branches, and repositories from any MCP client
MCP server for Bitbucket API integration - supports both Cloud and Server
A Model Context Protocol server for Bitbucket with read-only operations
MCP server for Bitbucket Cloud integration
More in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.