mcp-jira-cloud-server
npm
v4.2.0
Published by phuc-nt — 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 interacting with Atlassian Jira (46 optimized tools across 4 specialized modules with enhanced AI client compatibility)
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 − 7 = 93. 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 |
|---|---|
| −6 | capability blast radius (high) — 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.
In the server's implementation (`dist/index.js:2571`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: var makeValidate = new Function( "self", "RULES", "formats", "root"
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 dist/index.js
Each tool and what it can reach — statically extracted from the published source.
addGadgetToDashboardno sensitive capabilityaddIssueCommentno sensitive capabilityaddIssuesToBacklogno sensitive capabilityaddIssueToSprintno sensitive capabilityassignIssueno sensitive capabilitycloseSprintno sensitive capabilitycreateDashboardno sensitive capabilitycreateFilterno sensitive capabilitycreateFixVersionno sensitive capabilitycreateIssueno sensitive capabilitycreateSprintno sensitive capabilitydeleteFilterno sensitive capabilitydeleteIssueno sensitive capabilityenhancedSearchIssuesno sensitive capabilityepicSearchAgileno sensitive capabilitygetAssignableUsersno sensitive capabilitygetBoardno sensitive capabilitygetBoardConfigurationno sensitive capabilitygetBoardIssuesno sensitive capabilitygetDashboardno sensitive capabilitygetDashboardGadgetsno sensitive capabilitygetFilterno sensitive capabilitygetIssueno sensitive capabilitygetIssueCommentsno sensitive capabilitygetIssueTransitionsno sensitive capabilitygetJiraGadgetsno sensitive capabilitygetMyFiltersno sensitive capabilitygetProjectno sensitive capabilitygetProjectVersionno sensitive capabilitygetSprintno sensitive capabilitygetSprintIssuesno sensitive capabilitygetUserno sensitive capabilitylistBacklogIssuesno sensitive capabilitylistBoardsno sensitive capabilitylistDashboardsno sensitive capabilitylistFiltersno sensitive capabilitylistIssuesno sensitive capabilitylistProjectsno sensitive capabilitylistProjectVersionsno sensitive capabilitylistSprintsno sensitive capabilityrankBacklogIssuesno sensitive capabilityremoveGadgetFromDashboardno sensitive capabilitystartSprintno sensitive capabilitytransitionIssueno sensitive capabilityuniversalSearchUsersno sensitive capabilityupdateDashboardno sensitive capabilityupdateFilterno sensitive capabilityupdateFixVersionno sensitive capabilityupdateIssueno sensitive capabilityupdateIssueCommentno 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 |
|---|---|---|---|---|
v4.2.0 latest |
A 93/100 | 1 | 1.13.0 | 2026-09-07 |
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-jira-cloud-server --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →
Model Context Protocol (MCP) server for Jira Cloud - enables AI assistants to interact with Jira
A model context provider (MCP) server to provide context between a Jira ticket and the GitHub Copilot Chat prompt.
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
MCP AgentChat - 让 AI Agent 通过 Telegram 与用户实时交互:发送消息、图片,等待用户回复
A Model Context Protocol (MCP) server for Airthings Air Quality Monitor devices.
MCP server for Anki
TypeScript package for reading and searching Apple Notes on macOS via direct SQLite access. Includes markdown conversion, attachment support, and offers a local MCP server!
Verified biotech catalyst calendar (PDUFA/AdComm/trial readouts) anchored to official sources.
Appointment booking platform letting agents check provider availability and create bookings.