Jiraxmcp MCP Server
jiraxmcp
npm
v0.2.5
Source verified
Published by vaibhavpandeyvpz — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
TypeScript stdio MCP server and CLI for Jira Cloud.
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:
| Points | Adoption-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_batch_get_changelogs, jira_download_attachments]) co-exist with external-action tools ([jira_create_issue, jira_batch_create_issues, jira_create_issue_link]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [jira_batch_get_changelogs, jira_download_attachments] → sinks [jira_create_issue, jira_batch_create_issues, jira_create_issue_link]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow jira_batch_get_changelogs → jira_create_issue
Tools 31
Each tool and what it can reach — statically extracted from the published source.
jira_batch_create_issuesnetwork egressjira_batch_get_changelogsingests untrusted inputjira_create_issuenetwork egressjira_create_issue_linknetwork egressjira_download_attachmentsingests untrusted inputjira_add_commentno sensitive capabilityjira_add_issues_to_sprintno sensitive capabilityjira_create_remote_issue_linkno sensitive capabilityjira_create_sprintno sensitive capabilityjira_delete_issueno sensitive capability
Show 21 more tools ↓
jira_edit_commentno sensitive capabilityjira_get_agile_boardsno sensitive capabilityjira_get_all_projectsno sensitive capabilityjira_get_board_issuesno sensitive capabilityjira_get_field_optionsno sensitive capabilityjira_get_issueno sensitive capabilityjira_get_issue_imagesno sensitive capabilityjira_get_link_typesno sensitive capabilityjira_get_project_issuesno sensitive capabilityjira_get_sprint_issuesno sensitive capabilityjira_get_sprints_from_boardno sensitive capabilityjira_get_transitionsno sensitive capabilityjira_get_user_profileno sensitive capabilityjira_link_to_epicno sensitive capabilityjira_remove_issue_linkno sensitive capabilityjira_search_fieldsno sensitive capabilityjira_search_issuesno sensitive capabilityjira_search_usersno sensitive capabilityjira_transition_issueno sensitive capabilityjira_update_issueno sensitive capabilityjira_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
- Tools were statically extracted from the published source (31 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 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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.2.5 latest |
A 97/100 | 1 | 1.13.0 | 2026-09-08 |
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 jiraxmcp --onlineMore 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.