Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Lexmata/bitbucket-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/lexmata/bitbucket-mcp/bitbucket-mcp)<a href="https://agentmods.dev/mcp/lexmata/bitbucket-mcp/bitbucket-mcp"><img src="https://agentmods.dev/badge/mcp/lexmata/bitbucket-mcp/bitbucket-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/lexmata/bitbucket-mcp/bitbucket-mcp"><img src="https://agentmods.dev/badge/mcp/lexmata/bitbucket-mcp/bitbucket-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bitbucket-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- mcp — 88% identical, 4 lines differ
What it actually says
{ "bitbucket-mcp": { "command": "npx", "args": [ "-y", "@lexmata/bitbucket-mcp" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 9 lines scan A 26185f077572
bitbucket-mcp is an MCP server published in the GitHub repository Lexmata/bitbucket-mcp (1 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
atlassian-server-mcp
Unified stdio MCP server for Jira, Confluence, and Bitbucket Data Center. Runs locally from the @zaimokuza/atlassian-server-mcp npm package.
atlassian-mcp-server
Connect to Atlassian Jira, Confluence, and Compass to search, create, and manage your work. Remote server at mcp.atlassian.com.
atlassian-mcp-server
MCP server for Atlassian APIs (Jira, Confluence, Bitbucket). Runs locally from the @jagadeesh52423/atlassian-mcp-server npm package.
bitbucket-mcp
MCP server for Bitbucket Cloud REST API — works with any MCP client. Runs locally from the @or2ooo/bitbucket-mcp npm package.
atlassian-dc-mcp-bitbucket
MCP server for Atlassian Bitbucket Data Center - interact with repositories and code. Runs locally from the bitbucket-datacenter-mcp npm package. Needs 4 environment variables to run.
atlassian-dc-mcp-jira
MCP server for Atlassian Jira Data Center - search, view, and create issues. Runs locally from the jira-datacenter-mcp npm package. Needs 4 environment variables to run.