Bitbucket Dc (shibainu16) MCP Server
@shibainu16/bitbucket-dc-mcp
npm
v1.4.0
Published by @shibainu16 — 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.
HTTP MCP server for Bitbucket Data Center REST API
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 − 4 = 96. 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 |
|---|---|
| −3 | capability blast radius (moderate) — 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 1
medium Dynamic module load from a non-literal (build/registry/helpers.js)MTC-SRC-005
In the server's implementation (`build/registry/helpers.js:103`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: Path); return await import(fileUrl); } /** * Logs that a module is being loaded * @param moduleType - The type of
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/registry/helpers.js
Tools 59
Each tool and what it can reach — statically extracted from the published source.
browseFilesingests untrusted inputaddBlockerCommentno sensitive capabilityaddPRCommentno sensitive capabilityaddPullRequestReviewersno sensitive capabilityapprovePullRequestno sensitive capabilitycanMergePullRequestno sensitive capabilitycreateBranchno sensitive capabilitycreateProjectno sensitive capabilitycreatePullRequestno sensitive capabilitycreateRepositoryno sensitive capability
Show 49 more tools ↓
createTagno sensitive capabilitydeclinePullRequestno sensitive capabilitydeleteBranchno sensitive capabilitydeletePRCommentno sensitive capabilitydiscardReviewno sensitive capabilityeditFileno sensitive capabilityfinishReviewno sensitive capabilityforkRepositoryno sensitive capabilitygetBuildStatusesno sensitive capabilitygetBuildStatusStatsno sensitive capabilitygetCommitno sensitive capabilitygetCommitChangesno sensitive capabilitygetCommitDiffno sensitive capabilitygetDefaultBranchno sensitive capabilitygetFileContentno sensitive capabilitygetPRCommentno sensitive capabilitygetProjectno sensitive capabilitygetPullRequestno sensitive capabilitygetPullRequestActivityno sensitive capabilitygetPullRequestChangesno sensitive capabilitygetPullRequestCommitsno sensitive capabilitygetPullRequestDiffno sensitive capabilitygetPullRequestParticipantsno sensitive capabilitygetPullRequestPatchno sensitive capabilitygetRepositoryno sensitive capabilitylistBranchesno sensitive capabilitylistCommitsno sensitive capabilitylistFilesno sensitive capabilitylistPendingReviewCommentsno sensitive capabilitylistPRCommentsno sensitive capabilitylistProjectsno sensitive capabilitylistPRTasksno sensitive capabilitylistPullRequestsno sensitive capabilitylistRepositoriesno sensitive capabilitylistTagsno sensitive capabilitymarkPullRequestAsDraftno sensitive capabilitymergePullRequestno sensitive capabilityreopenPRCommentno sensitive capabilityreopenPullRequestno sensitive capabilityreopenTaskno sensitive capabilityresolvePRCommentno sensitive capabilityresolveTaskno sensitive capabilitysetDefaultBranchno sensitive capabilitystartReviewno sensitive capabilitystreamPullRequestDiffno sensitive capabilityunapprovePullRequestno sensitive capabilityupdatePRCommentno sensitive capabilityupdateProjectno sensitive capabilityupdatePullRequestno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (59 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 |
|---|---|---|---|---|
v1.4.0 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-09 |
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 @shibainu16/bitbucket-dc-mcp --onlineOther implementations of Bitbucket Dc 2
Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →
MCP server for Bitbucket Data Center — code search, file browsing, PRs, commits, and more.
Bitbucket DataCenter MCP Server with semantic search and operation execution
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.
Generates production-ready UI components from natural language, inspired by v0.
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.