Jira Cloud (tezaswiraj7222) MCP Server

mcp-jira-cloud npm v4.4.0 Source verified

Published by tezaswiraj7222 — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

A Model Context Protocol (MCP) server for Jira Cloud integration. Enables AI assistants like GitHub Copilot and Claude to search issues, manage tickets, log work, handle sprints, and interact with your Jira instance seamlessly. Features 91 tools for compr

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/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 = 97/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 − 3 = 97. 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

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 ([jira_get_attachment_content]) co-exist with external-action tools ([jira_create_issue, jira_create_issue_link]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [jira_get_attachment_content] → sinks [jira_create_issue, jira_create_issue_link]

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

Location: flow jira_get_attachment_content → jira_create_issue

Tools 91

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

  • jira_create_issuenetwork egress
  • jira_create_issue_linknetwork egress
  • jira_get_attachment_contentingests untrusted input
  • _internal_jira_set_authno sensitive capability
  • jira_add_commentno sensitive capability
  • jira_add_dashboard_gadgetno sensitive capability
  • jira_add_labelsno sensitive capability
  • jira_add_voteno sensitive capability
  • jira_add_watcherno sensitive capability
  • jira_add_worklogno sensitive capability
Show 81 more tools ↓
  • jira_assign_issueno sensitive capability
  • jira_auth_statusno sensitive capability
  • jira_autocomplete_jqlno sensitive capability
  • jira_bulk_edit_issuesno sensitive capability
  • jira_bulk_unwatch_issuesno sensitive capability
  • jira_bulk_watch_issuesno sensitive capability
  • jira_clear_authno sensitive capability
  • jira_complete_sprintno sensitive capability
  • jira_create_filterno sensitive capability
  • jira_create_sprintno sensitive capability
  • jira_get_all_labelsno sensitive capability
  • jira_get_attachment_metadatano sensitive capability
  • jira_get_attachmentsno sensitive capability
  • jira_get_backlog_issuesno sensitive capability
  • jira_get_boardno sensitive capability
  • jira_get_board_configurationno sensitive capability
  • jira_get_boardsno sensitive capability
  • jira_get_bulk_operation_progressno sensitive capability
  • jira_get_changelogno sensitive capability
  • jira_get_componentsno sensitive capability
  • jira_get_create_metadatano sensitive capability
  • jira_get_dashboardno sensitive capability
  • jira_get_dashboard_gadgetsno sensitive capability
  • jira_get_dashboardsno sensitive capability
  • jira_get_deleted_worklog_idsno sensitive capability
  • jira_get_edit_metadatano sensitive capability
  • jira_get_epic_issuesno sensitive capability
  • jira_get_epicsno sensitive capability
  • jira_get_favourite_filtersno sensitive capability
  • jira_get_fieldsno sensitive capability
  • jira_get_filterno sensitive capability
  • jira_get_filtersno sensitive capability
  • jira_get_issueno sensitive capability
  • jira_get_issue_commentsno sensitive capability
  • jira_get_issue_linksno sensitive capability
  • jira_get_issue_summaryno sensitive capability
  • jira_get_issue_typesno sensitive capability
  • jira_get_issue_worklogsno sensitive capability
  • jira_get_link_typesno sensitive capability
  • jira_get_my_filtersno sensitive capability
  • jira_get_my_open_issuesno 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_sprintsno sensitive capability
  • jira_get_statusesno sensitive capability
  • jira_get_transitionsno sensitive capability
  • jira_get_updated_worklog_idsno sensitive capability
  • jira_get_user_worklogsno sensitive capability
  • jira_get_versionsno sensitive capability
  • jira_get_votesno sensitive capability
  • jira_get_watchersno sensitive capability
  • jira_get_worklogs_by_idsno sensitive capability
  • jira_list_projectsno sensitive capability
  • jira_move_issues_to_backlogno sensitive capability
  • jira_move_issues_to_epicno sensitive capability
  • jira_move_issues_to_sprintno sensitive capability
  • jira_oauth_exchange_codeno sensitive capability
  • jira_oauth_get_auth_urlno sensitive capability
  • jira_oauth_list_sitesno sensitive capability
  • jira_oauth_refreshno sensitive capability
  • jira_oauth_set_tokensno sensitive capability
  • jira_parse_jqlno sensitive capability
  • jira_rank_issuesno sensitive capability
  • jira_remove_issues_from_epicno sensitive capability
  • jira_remove_voteno sensitive capability
  • jira_remove_watcherno sensitive capability
  • jira_resolveno sensitive capability
  • jira_search_dashboardsno sensitive capability
  • jira_search_issuesno sensitive capability
  • jira_search_issues_summaryno sensitive capability
  • jira_search_usersno sensitive capability
  • jira_start_sprintno sensitive capability
  • jira_transition_issueno sensitive capability
  • jira_update_filterno sensitive capability
  • jira_update_issueno sensitive capability
  • jira_update_sprintno sensitive capability
  • jira_upload_attachmentno sensitive capability
  • jira_validate_jqlno sensitive capability
  • jira_whoamino 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
v4.4.0 latest A 97/100 1 1.13.0 2026-09-07

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

Use the free API → How scoring works

Other implementations of Jira Cloud 3

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

More in Developer Tools