Jira (cuongph.dev) MCP Server
@cuongph.dev/jira-mcp
npm
v0.1.15
Published by @cuongph.dev — 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 internal Jira 8 via SSO session bootstrap with Playwright
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:
| Points | Adoption-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 ([jira_get_issue, jira_get_audit_context]) co-exist with external-action tools ([jira_create_issue, jira_preview_create_issue, jira_preview_adf, jira_sync_gitlab_review_defects]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [jira_get_issue, jira_get_audit_context] → sinks [jira_create_issue, jira_preview_create_issue, jira_preview_adf, jira_sync_gitlab_review_defects]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow jira_get_issue → jira_create_issue
Tools 47
Each tool and what it can reach — statically extracted from the published source.
jira_create_issuenetwork egressjira_get_audit_contextingests untrusted inputjira_get_issueingests untrusted inputjira_preview_adfnetwork egressjira_preview_create_issuenetwork egressjira_sync_gitlab_review_defectsnetwork egressjira_act_on_timesheet_approvalno sensitive capabilityjira_add_attachmentno sensitive capabilityjira_add_commentno sensitive capabilityjira_add_comment_with_fileno sensitive capability
Show 37 more tools ↓
jira_add_commentsno sensitive capabilityjira_add_worklogno sensitive capabilityjira_assign_issueno sensitive capabilityjira_bulk_link_issuesno sensitive capabilityjira_bulk_transition_issuesno sensitive capabilityjira_bulk_update_issue_fieldsno sensitive capabilityjira_clone_issueno sensitive capabilityjira_create_subtaskno sensitive capabilityjira_delete_commentno sensitive capabilityjira_delete_issueno sensitive capabilityjira_delete_worklogno sensitive capabilityjira_export_project_timesheetno sensitive capabilityjira_find_userno sensitive capabilityjira_get_commentsno sensitive capabilityjira_get_componentsno sensitive capabilityjira_get_create_metano sensitive capabilityjira_get_edit_metano sensitive capabilityjira_get_issue_contextno sensitive capabilityjira_get_issue_linksno sensitive capabilityjira_get_my_worklogsno sensitive capabilityjira_get_prioritiesno sensitive capabilityjira_get_projectsno sensitive capabilityjira_get_subtasksno sensitive capabilityjira_get_timesheet_approval_logno sensitive capabilityjira_get_timesheet_approvalsno sensitive capabilityjira_get_transitionsno sensitive capabilityjira_link_issuesno sensitive capabilityjira_search_issuesno sensitive capabilityjira_search_tempo_teamsno sensitive capabilityjira_search_worklogsno sensitive capabilityjira_smart_searchno sensitive capabilityjira_transition_issueno sensitive capabilityjira_update_commentno sensitive capabilityjira_update_issue_fieldsno sensitive capabilityjira_update_worklogno sensitive capabilityjira_upload_attachment_contentno sensitive capabilityjira_validate_issue_updateno 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
- Tools were statically extracted from the published source (47 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.15 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-07 |
v0.1.14 |
A 96/100 | 1 | 1.12.1 | 2026-08-13 |
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.
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 @cuongph.dev/jira-mcp --onlineOther implementations of Jira 44
Independent packages implementing the same tool, scanned with the same engine. Compare all 45 side by side →
Community-maintained MCP server for Atlassian Jira Data Center. Not affiliated with Atlassian.
Model Context Protocol (MCP) server for Jira Cloud API v3 with automatic Markdown-to-ADF conversion
MCP server for managing Jira Stories, sprints and boards in a self-hosted Jira instance (PRD automation workflow)
MCP server for Jira API integration - supports Jira Cloud
A comprehensive Model Context Protocol server for Jira integration with issue management, board operations, time tracking, and project management capabilities
Jira MCP Server
More in Productivity & Workflow
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.