Jira (avidian) MCP Server

@avidian/mcp-jira npm v0.10.1 Source verified

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

MCP server for Jira Cloud — gives AI agents full context and control over Jira issues, projects, sprints, and workflows.

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 ([get_image, get_text_file, get_video, get_binary_file]) 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_image, get_text_file, get_video, get_binary_file] → sinks [create_issue]

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

Location: flow get_image → create_issue

Tools 59

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

  • create_issuenetwork egress
  • get_binary_fileingests untrusted input
  • get_imageingests untrusted input
  • get_text_fileingests untrusted input
  • get_videoingests untrusted input
  • add_attachmentno sensitive capability
  • add_commentno sensitive capability
  • add_issues_to_epicno sensitive capability
  • add_remote_linkno sensitive capability
  • add_voteno sensitive capability
Show 49 more tools ↓
  • add_watcherno sensitive capability
  • add_worklogno sensitive capability
  • assign_issueno sensitive capability
  • complete_sprintno sensitive capability
  • create_componentno sensitive capability
  • create_sprintno sensitive capability
  • create_versionno sensitive capability
  • delete_attachmentno sensitive capability
  • delete_commentno sensitive capability
  • delete_issueno sensitive capability
  • delete_issue_linkno sensitive capability
  • delete_worklogno sensitive capability
  • get_boardno sensitive capability
  • get_create_metano sensitive capability
  • get_current_userno sensitive capability
  • get_issueno sensitive capability
  • get_issue_changelogno sensitive capability
  • get_issue_commentsno sensitive capability
  • get_issue_transitionsno sensitive capability
  • get_link_typesno sensitive capability
  • get_projectno sensitive capability
  • get_sprintno sensitive capability
  • get_userno sensitive capability
  • get_votesno sensitive capability
  • get_worklogsno sensitive capability
  • link_issuesno sensitive capability
  • list_assignable_usersno sensitive capability
  • list_attachmentsno sensitive capability
  • list_boardsno sensitive capability
  • list_componentsno sensitive capability
  • list_fieldsno sensitive capability
  • list_issue_typesno sensitive capability
  • list_labelsno sensitive capability
  • list_prioritiesno sensitive capability
  • list_projectsno sensitive capability
  • list_statusesno sensitive capability
  • list_versionsno sensitive capability
  • list_watchersno sensitive capability
  • move_issues_to_backlogno sensitive capability
  • move_issues_to_sprintno sensitive capability
  • remove_voteno sensitive capability
  • remove_watcherno sensitive capability
  • search_issuesno sensitive capability
  • start_sprintno sensitive capability
  • transition_issueno sensitive capability
  • update_commentno sensitive capability
  • update_issueno sensitive capability
  • update_versionno sensitive capability
  • update_worklogno 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 4

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
v0.10.1 latest A 97/100 1 1.13.0 2026-09-07
v0.10.0 A 97/100 1 1.13.0 2026-08-25
v0.9.0 A 97/100 1 1.12.1 2026-08-12
v0.8.4 A 97/100 1 1.12.1 2026-07-28

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

Use the free API → How scoring works

Other implementations of Jira 44

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

More in Productivity & Workflow