mcp-atlassian-ry
PyPI
v0.0.1.dev570
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.
The Model Context Protocol (MCP) Atlassian integration is an open-source implementation that bridges Atlassian products (Jira and Confluence) with AI language models following Anthropic's MCP specification. This project enables secure, contextual AI interactions with Atlassian tools while maintaining data privacy and security. Key features include:
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:
| Points | Adoption-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.
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/unit/confluence/test_client.py:300`): 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
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/unit/jira/test_client.py:328`): 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
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
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", "mcp-atlassian"], input=_build_probe_payload(),
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
Each tool and what it can reach — statically extracted from the published source.
download_attachmentingests untrusted inputdownload_attachmentsingests untrusted inputdownload_content_attachmentsingests untrusted inputget_pageingests untrusted inputget_page_childreningests untrusted inputget_page_diffingests untrusted inputget_page_historyingests untrusted inputget_page_imagesingests untrusted inputget_page_viewsingests untrusted inputbatch_get_changelogsno sensitive capabilityget_agile_boardsno sensitive capabilityget_all_projectsno sensitive capabilityget_attachmentsno sensitive capabilityget_board_issuesno sensitive capabilityget_commentsno sensitive capabilityget_field_optionsno sensitive capabilityget_issueno sensitive capabilityget_issue_datesno sensitive capabilityget_issue_development_infono sensitive capabilityget_issue_imagesno sensitive capabilityget_issue_proforma_formsno sensitive capabilityget_issue_slano sensitive capabilityget_issue_watchersno sensitive capabilityget_issues_development_infono sensitive capabilityget_labelsno sensitive capabilityget_link_typesno sensitive capabilityget_proforma_form_detailsno sensitive capabilityget_project_componentsno sensitive capabilityget_project_issuesno sensitive capabilityget_project_versionsno sensitive capabilityget_queue_issuesno sensitive capabilityget_requirementno sensitive capabilityget_service_desk_for_projectno sensitive capabilityget_service_desk_queuesno sensitive capabilityget_space_page_treeno sensitive capabilityget_sprint_issuesno sensitive capabilityget_sprints_from_boardno sensitive capabilityget_transitionsno sensitive capabilityget_user_profileno sensitive capabilityget_worklogno sensitive capabilitysearchno sensitive capabilitysearch_fieldsno sensitive capabilitysearch_requirementsno sensitive capabilitysearch_userno sensitive capabilityScan 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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.0.1.dev570 latest |
A 95/100 | 4 | 1.13.0 | 2026-08-25 |
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.
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-ry --online --registry pypi
Free public tax reference data — GST/VAT, income, company and capital-gains tax rules for 50+ countries.
The approval gate for unattended UCP buying agents — a policy/approval MCP proxy in front of a merchant's UCP checkout endpoint.
Autotask PSA MCP server. Generic entity query/get/create/update across the full REST API plus convenience tools for tickets, companies, contacts, projects, tasks and time entries. AI-safe with readonly mode and destructive-action confirmation. stdio + opt
MCP server for B2C Commerce developer experience tools
Search, compare and contact real-world companies through a public MCP business directory.
Norwegian business register (Brønnøysundregistrene) as an MCP server — companies, roles, subunits and annual accounts, with the register's silent traps encoded as guards.