Atlassian (Jira & Confluence) (PyPI) MCP Server

mcp-atlassian PyPI v0.23.1

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Community Atlassian server: Jira issues and Confluence pages over MCP.

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 95/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 5

low Reads a sensitive credential path or dumps the environment in packaging/dev tooling (tests/unit/confluence/test_client.py)MTC-SRC-006

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/unit/confluence/test_client.py:338`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: les trust_env to prevent .netrc override (#860).""" with ( patch("mcp_atlassian.confluence.client.Confluence

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/unit/confluence/test_client.py

low Reads a sensitive credential path or dumps the environment in packaging/dev tooling (tests/unit/jira/test_client.py)MTC-SRC-006

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/unit/jira/test_client.py:447`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: les trust_env to prevent .netrc override (#860).""" with ( patch("mcp_atlassian.jira.client.Jira") as mock_j

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/unit/jira/test_client.py

low Shell/command execution in packaging/dev tooling (tests/unit/jira/test_attachments.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/unit/jira/test_attachments.py:1391`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: n_value = [b"import os; os.system('id')\n"] mock_response.raise_for_status = MagicMock() attachments_mix

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/unit/jira/test_attachments.py

low Shell/command execution in packaging/dev tooling (tests/unit/test_stdin_monitoring_fix.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/unit/test_stdin_monitoring_fix.py:42`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: pt result = subprocess.run( [sys.executable, test_script], capture_output=Tr

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/unit/test_stdin_monitoring_fix.py

low Shell/command execution in packaging/dev tooling (tests/unit/test_stdio_lifecycle.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/unit/test_stdio_lifecycle.py:34`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: } ) result = subprocess.run( ["uv", "run", "--frozen", "mcp-atlassian"], input=_build_probe_p

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/unit/test_stdio_lifecycle.py

Tools 57

Each tool and what it can reach — statically extracted from the published source.

  • download_attachmentingests untrusted input
  • download_attachmentsingests untrusted input
  • download_content_attachmentsingests untrusted input
  • get_pageingests untrusted input
  • get_page_childreningests untrusted input
  • get_page_diffingests untrusted input
  • get_page_historyingests untrusted input
  • get_page_imagesingests untrusted input
  • get_page_restrictionsingests untrusted input
  • get_page_templateingests untrusted input
Show 47 more tools ↓
  • get_page_viewsingests untrusted input
  • batch_get_changelogsno sensitive capability
  • check_content_permissionsno sensitive capability
  • get_agile_boardsno sensitive capability
  • get_all_projectsno sensitive capability
  • get_attachmentsno sensitive capability
  • get_board_issuesno sensitive capability
  • get_commentsno sensitive capability
  • get_create_fieldsno sensitive capability
  • get_cross_project_dependenciesno sensitive capability
  • get_field_optionsno sensitive capability
  • get_inline_commentsno sensitive capability
  • get_issueno sensitive capability
  • get_issue_datesno sensitive capability
  • get_issue_development_infono sensitive capability
  • get_issue_imagesno sensitive capability
  • get_issue_proforma_formsno sensitive capability
  • get_issue_slano sensitive capability
  • get_issue_watchersno sensitive capability
  • get_issues_development_infono sensitive capability
  • get_labelsno sensitive capability
  • get_link_typesno sensitive capability
  • get_proforma_form_detailsno sensitive capability
  • get_project_componentsno sensitive capability
  • get_project_epic_hierarchyno sensitive capability
  • get_project_fieldsno sensitive capability
  • get_project_issue_typesno sensitive capability
  • get_project_issuesno sensitive capability
  • get_project_versionsno sensitive capability
  • get_queue_issuesno sensitive capability
  • get_request_type_fieldsno sensitive capability
  • get_request_typesno sensitive capability
  • get_service_desk_for_projectno sensitive capability
  • get_service_desk_queuesno sensitive capability
  • get_space_page_treeno sensitive capability
  • get_space_permissionsno sensitive capability
  • get_sprint_issuesno sensitive capability
  • get_sprints_from_boardno sensitive capability
  • get_transitionsno sensitive capability
  • get_user_profileno sensitive capability
  • get_worklogno sensitive capability
  • list_page_templatesno sensitive capability
  • searchno sensitive capability
  • search_assignable_usersno sensitive capability
  • search_fieldsno sensitive capability
  • search_projectsno sensitive capability
  • search_userno sensitive capability

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.23.1 latest A 95/100 5 1.13.0 2026-08-25
v0.23.0 A 95/100 5 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-atlassian/badge.svg)](https://mcptrustchecker.com/registry/mcp-atlassian)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-atlassian"><img src="https://mcptrustchecker.com/registry/mcp-atlassian/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-atlassian/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-atlassian --online --registry pypi

Use the free API → How scoring works

Other implementations of Atlassian (Jira & Confluence) 13

Independent packages implementing the same tool, scanned with the same engine. Compare all 14 side by side →

More in Productivity & Workflow