npm analyzed 2.2.0

@nexus2520/bitbucket-mcp-server

v2.2.0
npm

MCP server for Bitbucket API integration - supports both Cloud and Server

maintainer
roshan84ya
license
MIT
first seen
2026-05-22
last seen
2026-06-14
releases · 30d
1
short id
risk60/100 · heuristic grade
D high
  • capability exposureinferred+28
  • inherited (deps)attested+15
  • tool safetyinferred+25
  • trust mitigatorsmixed−8

attestedinferredmixed

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

graded 12m ago · see ecosystem CVEs →

capability exposuregrade factor +28
Inferred surface — each links to servers holding it:
vulnerabilities0 CVEs

no known CVEs for this server.

inherited (deps) · grade factor +15

inherited via dependencies3
HIGH
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse via @modelcontextprotocol/sdk · 1 hop CVE-2026-25536 fixed in 1.26.0
HIGH
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability via @modelcontextprotocol/sdk · 1 hop CVE-2026-0621 fixed in 1.25.2
HIGH
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default via @modelcontextprotocol/sdk · 1 hop CVE-2025-66414 fixed in 1.24.0
tool safety4 findings · grade factor +25
  1. highexfiltration comboget_pull_request

    single tool reads + sends: fs, net

  2. highexfiltration combosearch_files

    single tool reads + sends: fs, net

  3. highexfiltration combosearch_code

    single tool reads + sends: fs, net

  4. highexfiltration combofind_in_files

    single tool reads + sends: fs, net

embed badgereadme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/npm:@nexus2520/bitbucket-mcp-server/badge.svg)](https://mcpobservatory.com/servers/npm:@nexus2520/bitbucket-mcp-server/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of roshan84ya.