Jira
NPM · @PIPEWORX/MCP-JIRA · 2 COMPONENTS
Jira MCP Pack
Available components
Last scanned (3 hours ago)
Scores higher than 82% of npm servers
Category Project Management
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-jira). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 349 tokens (~87/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 81
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-jira@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-jira |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-jira/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649472221 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:51162337908c248ff84834a843cbb6645ead18700ebb3e10261b5d83db5d7be2a2ccb00c9b6c4fd487603d3310b372aff44e140b3f651e2d4e93c9e8f |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
jira_get_issue ~81
Get full details for a Jira issue by key (e.g., 'PROJ-123'). Returns description, status, assignee, priority, comments, attachments, and linked issues.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Comma-separated field names to include (optional) |
| issue_key | string | yes | Issue key (e.g., "PROJ-123") |
No output schema declared.
No examples provided.
jira_get_project ~65
Get details for a specific Jira project by key (e.g., 'PROJ') or ID. Returns name, description, lead, issue types, and custom fields.
| Name | Type | Req | Description |
|---|---|---|---|
| project_key | string | yes | Project key (e.g., "PROJ") or numeric project ID |
No output schema declared.
No examples provided.
jira_list_projects ~34
List all accessible Jira projects. Returns project keys, names, descriptions, and types. Use before searching to discover available projects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jira_search ~118
Search Jira issues using JQL queries. Returns issue keys, summaries, status, assignee, and priority. Use to find tasks by project, status, assignee, or custom criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Comma-separated field names to include (e.g., "summary,status,assignee") |
| jql | string | yes | JQL query (e.g., "project = PROJ AND status = Open ORDER BY created DESC") |
| max_results | number | – | Maximum results to return (default 20, max 100) |
No output schema declared.
No examples provided.
How do I install the Jira MCP server?
Jira runs locally as an npm package, launched with npx -y @pipeworx/mcp-jira. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-jira
claude mcp add pipeworx-io-jira -- npx -y @pipeworx/mcp-jira
What is the Jira MCP server?
Jira is an MCP server listed in the public MCP registry as io.github.pipeworx-io/jira. Jira MCP Pack. This page covers its npm package (@pipeworx/mcp-jira).
Is the Jira MCP server safe to use?
Jira scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Jira MCP server expose?
Jira exposes 4 tools: jira_search, jira_get_issue, jira_list_projects, jira_get_project. Their descriptions and schemas cost roughly 298 tokens of context every time the server is loaded.
Is the Jira MCP server still maintained?
Jira is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Jira MCP server under?
Jira declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.