Jira Extended MCP Server

jira-extended-mcp PyPI v0.3.2

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Extended Jira MCP Server - Full CRUD, bulk ops, sprints, releases, and more

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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 = 95/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 − 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:

PointsAdoption-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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 27

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

  • create_issuenetwork egress
  • create_issues_bulknetwork egress
  • add_commentno sensitive capability
  • add_worklogno sensitive capability
  • bulk_transitionno sensitive capability
  • create_versionno sensitive capability
  • delete_issueno sensitive capability
  • delete_issue_linkno sensitive capability
  • delete_versionno sensitive capability
  • get_boardsno sensitive capability
Show 17 more tools ↓
  • get_commentsno sensitive capability
  • get_createmetano sensitive capability
  • get_current_userno sensitive capability
  • get_issueno sensitive capability
  • get_issue_linksno sensitive capability
  • get_projectno sensitive capability
  • get_projectsno sensitive capability
  • get_sprintsno sensitive capability
  • get_transitionsno sensitive capability
  • get_versionsno sensitive capability
  • link_issuesno sensitive capability
  • move_to_sprintno sensitive capability
  • search_issuesno sensitive capability
  • search_usersno sensitive capability
  • transition_issueno sensitive capability
  • update_issueno sensitive capability
  • update_versionno sensitive capability

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v0.3.2 latest A 95/100 0 1.13.0 2026-08-25

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 · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/jira-extended-mcp/badge.svg)](https://mcptrustchecker.com/registry/jira-extended-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/jira-extended-mcp"><img src="https://mcptrustchecker.com/registry/jira-extended-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/jira-extended-mcp/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 jira-extended-mcp --online --registry pypi

Use the free API → How scoring works

More in Productivity & Workflow