Atlassian Attachments
PYPI · MCP-ATLASSIAN-ATTACHMENTS
MCP server for downloading, uploading, and deleting Jira Cloud attachments by ID.
Available components
Last scanned (22 hours ago)
Scores higher than 70% of PyPI servers
Category Documents and Files
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
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to alyiox/mcp-atlassian-attachments). View diagnostics → Pass
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 72 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 402 tokens (~100/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 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
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.
- 4 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- 2 Nov 26 −5
- Stability: pass → 0.60 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 23 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 21 Oct 26 0
- Security disclosure: fail → unverified ▼ 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 4 Nov 2026 · Analysed pypi/mcp-atlassian-attachments@0.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | alyiox/mcp-atlassian-attachments |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/alyiox/mcp-atlassian-attachments/.github/workflows/ci.yml@refs/tags/0.3.0 |
| Rekor log index | 2579700449 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:ffcad1e74944288418f3308324c7ec1718ac227fadb67a2c8344098ecff1aca2 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| 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 →
delete_jira_attachment ~41
[Atlassian] Delete Jira attachment by ID. Permanent, with no undo.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_id | string | yes | Jira attachment ID to delete permanently. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
download_jira_attachment ~96
[Atlassian] Download Jira attachment by ID to a local directory.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_id | string | yes | Jira attachment ID, for example 439535. |
| filename | – | – | Uses Jira metadata filename when omitted. |
| output_dir | string | yes | Local directory to save the file. Created automatically if it does not exist. |
| overwrite | boolean | – | Replace an existing file when true. Fail if the file exists when false. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_jira_attachment_reference ~84
[Atlassian] Resolve Jira attachment ID into its ADF media UUID. For an attachment already on an issue; after an upload use the mediaId that upload_jira_attachment already returned instead of calling this. See that tool for the ADF media node shape.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_id | string | yes | Jira attachment ID, for example 439535. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
upload_jira_attachment ~181
[Atlassian] Upload local file as Jira attachment. Returns mediaId, the Media Services UUID needed to embed the file in an issue description or comment via a Jira content tool. An ADF media node references this UUID, never attachmentId: {"type":"media","attrs":{"type":"file","id":<mediaId>,"collection":"","alt":<filename>}} Wrap it in mediaSingle (image), mediaGroup (file card), or mediaInline (chip); a bare media node does not render. mediaId is null if it cannot be resolved.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the local file to upload. Must exist. |
| filename | – | – | Name to store in Jira. Uses the local filename when omitted. |
| issue_key | string | yes | Jira issue key or ID, for example PROJ-123. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Atlassian Attachments MCP server?
Atlassian Attachments runs locally as a PyPI package, launched with uvx mcp-atlassian-attachments. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-atlassian-attachments
claude mcp add alyiox-mcp-atlassian-attachments -- uvx mcp-atlassian-attachments
What is the Atlassian Attachments MCP server?
Atlassian Attachments is an MCP server listed in the public MCP registry as io.github.alyiox/mcp-atlassian-attachments. MCP server for downloading, uploading, and deleting Jira Cloud attachments by ID. This page covers its PyPI package (mcp-atlassian-attachments).
Is the Atlassian Attachments MCP server safe to use?
Atlassian Attachments scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 Atlassian Attachments MCP server expose?
Atlassian Attachments exposes 4 tools: download_jira_attachment, upload_jira_attachment, get_jira_attachment_reference, delete_jira_attachment. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded.
Is the Atlassian Attachments MCP server still maintained?
Atlassian Attachments is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.