Atlassian (halim-23) MCP Server

atlassian-mcp PyPI v1.0.0

Published by halim-23 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Jira & Confluence — 53 tools for issue management, sprint planning, board management, and Confluence page management

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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 = 96/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 − 4 = 96. 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
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([confluence_get_page, confluence_get_page_labels, confluence_get_page_ancestors, confluence_get_page_comments]) co-exist with external-action tools ([jira_create_issue]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [confluence_get_page, confluence_get_page_labels, confluence_get_page_ancestors, confluence_get_page_comments] → sinks [jira_create_issue]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow confluence_get_page → jira_create_issue

Tools 53

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

  • confluence_get_pageingests untrusted input
  • confluence_get_page_ancestorsingests untrusted input
  • confluence_get_page_commentsingests untrusted input
  • confluence_get_page_labelsingests untrusted input
  • jira_create_issuenetwork egress
  • confluence_add_page_commentno sensitive capability
  • confluence_add_page_labelsno sensitive capability
  • confluence_create_pageno sensitive capability
  • confluence_delete_pageno sensitive capability
  • confluence_delete_page_labelno sensitive capability
Show 43 more tools ↓
  • confluence_get_child_pagesno sensitive capability
  • confluence_get_spaceno sensitive capability
  • confluence_get_space_by_keyno sensitive capability
  • confluence_list_pages_in_spaceno sensitive capability
  • confluence_list_spacesno sensitive capability
  • confluence_searchno sensitive capability
  • confluence_update_pageno sensitive capability
  • jira_add_commentno sensitive capability
  • jira_add_watcherno sensitive capability
  • jira_add_worklogno sensitive capability
  • jira_assign_issueno sensitive capability
  • jira_create_sprintno sensitive capability
  • jira_delete_commentno sensitive capability
  • jira_delete_issueno sensitive capability
  • jira_get_boardno sensitive capability
  • jira_get_board_backlogno sensitive capability
  • jira_get_board_issuesno sensitive capability
  • jira_get_commentsno sensitive capability
  • jira_get_current_userno sensitive capability
  • jira_get_fieldsno sensitive capability
  • jira_get_issueno sensitive capability
  • jira_get_issue_typesno sensitive capability
  • jira_get_labelsno sensitive capability
  • jira_get_link_typesno sensitive capability
  • jira_get_prioritiesno sensitive capability
  • jira_get_projectno sensitive capability
  • jira_get_sprintno sensitive capability
  • jira_get_sprint_issuesno sensitive capability
  • jira_get_transitionsno sensitive capability
  • jira_get_watchersno sensitive capability
  • jira_get_worklogsno sensitive capability
  • jira_link_issuesno sensitive capability
  • jira_list_boardsno sensitive capability
  • jira_list_projectsno sensitive capability
  • jira_list_sprintsno sensitive capability
  • jira_move_issues_to_backlogno sensitive capability
  • jira_move_issues_to_sprintno sensitive capability
  • jira_search_issuesno sensitive capability
  • jira_search_usersno sensitive capability
  • jira_transition_issueno sensitive capability
  • jira_update_commentno sensitive capability
  • jira_update_issueno sensitive capability
  • jira_update_sprintno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

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
v1.0.0 latest A 96/100 1 1.13.0 2026-08-25

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 · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/atlassian-mcp-2/badge.svg)](https://mcptrustchecker.com/registry/atlassian-mcp-2)
HTML
<a href="https://mcptrustchecker.com/registry/atlassian-mcp-2"><img src="https://mcptrustchecker.com/registry/atlassian-mcp-2/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/atlassian-mcp-2/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 atlassian-mcp --online --registry pypi

Use the free API → How scoring works

Other implementations of Atlassian 13

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

More in Productivity & Workflow