Jira (yashjhunjhunwala) MCP Server
@yashjhunjhunwala/jira-mcp-server
npm
v1.0.1
Published by @yashjhunjhunwala — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP server for Jira integration with attachment support
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.
Findings 1
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([get_attachments, download_attachment]) co-exist with external-action tools ([create_issue]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [get_attachments, download_attachment] → sinks [create_issue]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow get_attachments → create_issue
Tools 9
Each tool and what it can reach — statically extracted from the published source.
create_issuenetwork egressdownload_attachmentingests untrusted inputget_attachmentsingests untrusted inputadd_attachmentno sensitive capabilityadd_commentno sensitive capabilitydelete_commentno sensitive capabilityget_issueno sensitive capabilitysearch_issuesno sensitive capabilityupdate_issueno 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 (9 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 |
|---|---|---|---|---|
v1.0.1 latest |
A 95/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.
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 @yashjhunjhunwala/jira-mcp-server --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 Business & CRM
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.