bitbucket-server-mcp (Upendrasengar/bitbucket-server-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 118 tools. No publisher has claimed this listing.

C
Emerging
74/100
23 days ago

bitbucket-server-mcp

Enables to interact with Bitbucket Server repositories, pull requests, and code reviews, including file browsing, PR management, and review actions through natural language.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Upendrasengar

Source: Glama

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. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

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

// key findings
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.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configBITBUCKET_CACHE_TTLNo Cache duration in seconds (default: 300). Set to 0 to disable caching.
configBITBUCKET_CUSTOM_HEADERSNo Extra headers for all requests (Key=Value,Key2=Value2). Useful for Zero Trust tokens.
configBITBUCKET_DEFAULT_PROJECTNo Default project key when not specified in tool calls
configBITBUCKET_DIFF_MAX_LINES_PER_FILENo Max lines per file in diffs. Set to 0 for no limit.
configBITBUCKET_ENABLED_TOOLSNo Comma-separated list of tool names to enable. If not set, all tools are available.
🔐 secretBITBUCKET_PASSWORDYes Password for basic auth
configBITBUCKET_READ_ONLYNo Set to true to disable all write operations
configBITBUCKET_REQUEST_TIMEOUT
configBITBUCKET_STARTUP_HEALTHCHECKNo Set to true to run a connectivity check against Bitbucket on startup (default: false).
🔐 secretBITBUCKET_TOKENe =your-token \
configBITBUCKET_URLe =https://your-bitbucket-server.com \
configBITBUCKET_USERNAMEYes Username for basic auth
configGITHUB_REF_NAME
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

118/118 tools missing one or more hints — manage_comment (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_emoticons (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_commit_comments (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +115 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

98/118 tool handlers declare input schemas (83%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool test coverage

59/118 tools referenced in tests (50%)

Write tests that reference each tool by name so every tool has at least one test.

Domain consistency

npm scope @upendra_sengar doesn't match GitHub owner upendrasengar

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements 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/upendrasengar/bitbucket-server-mcp)](https://m8ven.ai/mcp/upendrasengar/bitbucket-server-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 9d3b2e1e1d7c23156e31d35ab50b269bc31ccef0
code hash: 38809d6813d887ed733ab988c54ad47ca841229bdd93972ec5ee66604f15680a
verified: 8/18/2026, 7:12:21 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client