com.mcparmory/bitbucket
PYPI · MCPARMORY-BITBUCKET · 2 COMPONENTS
Manage repositories, branches, webhooks, and pull requests in Bitbucket workspaces
Available components
Last scanned (12 hours ago)
Scores higher than 63% of PyPI servers
Category Version Control
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 2 of 45 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 177 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 31894 tokens (~122/item across 261 items; 261 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety96
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 42 of 51 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "list_deploy_keys" implies "deploy" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 261 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −18
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.77 functional
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 −1
- Stability: pass → 0.93 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/mcparmory-bitbucket@1.0.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 45 packages
| Packages resolved | 45 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
update_snippet Update Snippet ~101
Updates an existing snippet in the specified workspace, allowing changes to its title and files via differential payloads. Supports adding, updating, or deleting files atomically using JSON, multipart/related, or multipart/form-data content types.
| Name | Type | Req | Description |
|---|---|---|---|
| encoded_id | string | yes | The unique identifier of the snippet to update. |
| workspace | string | yes | The workspace identifier, either as a slug (e.g. a short name) or as a UUID surrounded by curly braces. |
No output schema declared.
No examples provided.
update_snippet_at_revision Update Snippet at Revision ~132
Updates a snippet only if the specified commit revision matches the current HEAD, acting as a Compare-And-Swap (CAS) operation to prevent overwriting concurrent modifications. Fails with a 405 if the provided revision is not the latest.
| Name | Type | Req | Description |
|---|---|---|---|
| encoded_id | string | yes | The unique identifier of the snippet to update. |
| node_id | string | yes | The SHA1 commit revision that must match the snippet's current HEAD; the update is rejected if this is not the most recent revision. |
| workspace | string | yes | The workspace identifier, either as a slug or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
update_snippet_comment Update Snippet Comment ~139
Updates an existing comment on a snippet. Only the comment's author can make updates, and the request body must include the `content.raw` field.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The request body containing the updated comment data. Must include `content.raw` with the new comment text in raw markup format. |
| comment_id | string | yes | The unique numeric identifier of the comment to update. |
| encoded_id | string | yes | The unique identifier of the snippet to which the comment belongs. |
| workspace | string | yes | The workspace identifier, either as a slug (e.g. a short name) or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
update_ssh_key Update SSH Key ~126
Updates the comment/label of a specific SSH public key on a user's account. Note that only the comment field can be modified; to change the key itself, delete and re-add it.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | Request body containing the SSH key fields to update. Only the comment/label field is supported for updates. |
| key_id | string | yes | The unique UUID identifier of the SSH key to update. |
| selected_user | string | yes | The account identifier for the target user, either as an Atlassian Account ID or as an account UUID surrounded by curly braces. |
No output schema declared.
No examples provided.
update_user_app_property Update User App Property ~138
Updates the value of a named application property stored against a specific user for a given Connect app. Use this to persist or overwrite app-specific metadata associated with a Bitbucket user account.
| Name | Type | Req | Description |
|---|---|---|---|
| app_key | string | yes | The key identifying the Connect app whose property is being updated. This must correspond to a registered Connect app key. |
| property_name | string | yes | The name of the application property to update. This identifies which property value will be overwritten for the specified user and app. |
| selected_user | string | yes | The unique identifier of the target user account, either as an Atlassian Account ID or a UUID wrapped in curly braces. |
No output schema declared.
No examples provided.
update_workspace_pipeline_variable Update Workspace Pipeline Variable ~93
Updates an existing pipeline configuration variable at the workspace level. Changes apply to all pipelines within the specified workspace that reference this variable.
| Name | Type | Req | Description |
|---|---|---|---|
| variable_uuid | string | yes | The UUID of the pipeline configuration variable to update, uniquely identifying the variable within the workspace. |
| workspace | string | yes | The unique identifier for the workspace, accepted as either a slug (human-readable short name) or a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
update_workspace_runner Update Workspace Runner ~91
Updates the configuration or metadata of a specific runner within a workspace. Use this to modify runner settings such as labels, status, or other properties.
| Name | Type | Req | Description |
|---|---|---|---|
| runner_uuid | string | yes | The unique identifier (UUID) of the runner to update within the specified workspace. |
| workspace | string | yes | The workspace identifier, either as a slug (human-readable short name) or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
update_workspace_webhook Update Workspace Webhook ~109
Updates an existing webhook subscription for a workspace, allowing modification of its description, URL, secret, active status, and subscribed events. The webhook secret is used to generate an HMAC hex digest signature sent in the X-Hub-Signature header on delivery.
| Name | Type | Req | Description |
|---|---|---|---|
| uid | string | yes | The unique identifier of the installed webhook subscription to update. |
| workspace | string | yes | The workspace identifier, either as a slug (human-readable short name) or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
upload_download_artifact Upload Download Artifact ~101
Upload one or more download artifacts to a repository using a multipart/form-data POST request. If a file with the same name already exists, it will be replaced.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository slug or UUID identifying the target repository. UUID values must be surrounded by curly-braces. |
| workspace | string | yes | The workspace ID (slug) or UUID identifying the workspace that owns the repository. UUID values must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
upsert_commit_report_annotation Upsert Commit Report Annotation ~232
Creates or updates a single annotation on a specific commit report, representing an individual finding such as a vulnerability, bug, or code smell, optionally linked to a file and line number.
| Name | Type | Req | Description |
|---|---|---|---|
| annotationId | string | yes | The unique identifier for this annotation, either its UUID or an external ID; prefix external IDs with your system name to avoid collisions. |
| body | object | – | The annotation payload containing fields such as title, summary, annotation_type (VULNERABILITY, CODE_SMELL, BUG), severity (CRITICAL, HIGH, MEDIUM, LOW), result (PASSED, FAILED, IGNORED, SKIPPED), a… |
| commit | string | yes | The full commit hash that the report and annotation belong to. |
| repo_slug | string | yes | The repository slug or identifier within the workspace. |
| reportId | string | yes | The unique identifier of the report to annotate, either its UUID or the external ID used when the report was created. |
| workspace | string | yes | The workspace identifier, either the slug or the UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
watch_snippet Watch Snippet ~78
Subscribes the authenticated user to watch a specific snippet, enabling notifications for changes. Returns 204 No Content on success.
| Name | Type | Req | Description |
|---|---|---|---|
| encoded_id | string | yes | The unique identifier of the snippet to watch. |
| workspace | string | yes | The workspace identifier, either as a slug (short name) or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
How do I install the com.mcparmory/bitbucket MCP server?
com.mcparmory/bitbucket runs locally as a PyPI package, launched with uvx mcparmory-bitbucket. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-bitbucket
claude mcp add com-mcparmory-bitbucket -- uvx mcparmory-bitbucket
What is the com.mcparmory/bitbucket MCP server?
com.mcparmory/bitbucket is an MCP server listed in the public MCP registry as com.mcparmory/bitbucket. Manage repositories, branches, webhooks, and pull requests in Bitbucket workspaces. This page covers its PyPI package (mcparmory-bitbucket).
Is the com.mcparmory/bitbucket MCP server safe to use?
com.mcparmory/bitbucket scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/bitbucket MCP server expose?
com.mcparmory/bitbucket exposes 261 tools: list_webhook_event_types, list_webhook_event_types_by_subject, list_workspace_repositories, get_repository, create_repository, and 256 more. Their descriptions and schemas cost roughly 31,894 tokens of context every time the server is loaded.
Is the com.mcparmory/bitbucket MCP server still maintained?
com.mcparmory/bitbucket is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mcparmory/bitbucket MCP server under?
com.mcparmory/bitbucket declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the com.mcparmory/bitbucket MCP server?
VerifyMCP ran 15 checks on com.mcparmory/bitbucket, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about com.mcparmory/bitbucket: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.