mcp-bitbucket (cleversondeveloper/mcp-bitbucket) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Limited view
71/100
21 days ago

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

cleversondeveloper

Source: github_code

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 1 credential: 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_WORKSPACEexport ="seu-workspace"
configBITBUCKET_TOKEN_FILENão - Caminho de arquivo com token (preferível BITBUCKET_TOKEN)
🔐 secretBITBUCKET_TOKENexport ="seu-token"
configBITBUCKET_API_BASENão https://api.bitbucket.org/2.0 Base da API Bitbucket
configBITBUCKET_CONNECT_TIMEOUTNão 10.0 Timeout de conexão (em segundos)
configBITBUCKET_READ_TIMEOUTNão 30.0 Timeout de leitura (em segundos)
configBITBUCKET_WRITE_TIMEOUTNão 30.0 Timeout de escrita (em segundos)
configBITBUCKET_CACHE_TTL
configBITBUCKET_MAX_RETRIESNão 3 Máximo de tentativas
configBITBUCKET_RETRY_BACKOFFNão 0.5 Fator base do backoff exponencial (em segundos)
configBITBUCKET_CONFIRM_PHRASENão I_UNDERSTAND Frase exigida em operações destrutivas
configBITBUCKET_ALLOWED_REPOSNão vazio Lista de repo_slug permitidos (CSV)
configBITBUCKET_ALLOWED_API_HOSTSNão api.bitbucket.org Hosts permitidos para BITBUCKET_API_BASE (CSV)
configBITBUCKET_MAX_CONNECTIONSNão 100 Limite total de conexões HTTP
configBITBUCKET_KEEPALIVE_EXPIRYNão 5.0 Expiração de keep-alive (em segundos)
configBITBUCKET_RATE_LIMIT_REQUESTSNão 120 Máximo de requests por janela
configBITBUCKET_MAX_RESPONSE_CHARSNão 100000 Limite de caracteres na resposta
// 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

23/23 tools missing one or more hints — list_branches (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_branch (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_branch (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +20 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 handlers catch errors

Only 0/23 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

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 4 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/cleversondeveloper-mcp-bitbucket-u1ravv)](https://m8ven.ai/mcp/cleversondeveloper-mcp-bitbucket-u1ravv)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: a8ddec79a5e4e7a3da6a820506a6a7177b9b76e6
code hash: 67932d41bd38736f93e65cd3d4391e23908fff9db3f6556a8caf2b8825ea06df
verified: 8/8/2026, 7:45:56 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