# Jira (npm · @pipeworx/mcp-jira)

Jira MCP Pack

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-jira/jira-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-jira/jira-mcp)
- npm · `@pipeworx/mcp-jira`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-jira/pipeworx-mcp-jira.md), [page](https://verifymcp.io/servers/pipeworx-io-jira/pipeworx-mcp-jira)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-jira`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-jira).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 349 tokens (~87/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-jira -- npx -y @pipeworx/mcp-jira
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-jira": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-jira"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-jira": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-jira"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-jira -- npx -y @pipeworx/mcp-jira
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-jira": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-jira"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-jira --command npx --arg -y --arg @pipeworx/mcp-jira
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-jira:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-jira"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-jira": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-jira"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-jira -t stdio -c npx -a -y @pipeworx/mcp-jira
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-jira": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-jira"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 84, +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.

### 2026-11-03 (score 83, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 68, −13)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 81)

First indexed and scored.

## MCP tools (4)

### `jira_search` (~118 tokens)

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.

Input parameters:

- `fields` (string): Comma-separated field names to include (e.g., "summary,status,assignee")
- `jql` (string, required): JQL query (e.g., "project = PROJ AND status = Open ORDER BY created DESC")
- `max_results` (number): Maximum results to return (default 20, max 100)

### `jira_get_issue` (~81 tokens)

Get full details for a Jira issue by key (e.g., 'PROJ-123'). Returns description, status, assignee, priority, comments, attachments, and linked issues.

Input parameters:

- `fields` (string): Comma-separated field names to include (optional)
- `issue_key` (string, required): Issue key (e.g., "PROJ-123")

### `jira_list_projects` (~34 tokens)

List all accessible Jira projects. Returns project keys, names, descriptions, and types. Use before searching to discover available projects.

### `jira_get_project` (~65 tokens)

Get details for a specific Jira project by key (e.g., 'PROJ') or ID. Returns name, description, lead, issue types, and custom fields.

Input parameters:

- `project_key` (string, required): Project key (e.g., "PROJ") or numeric project ID

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-jira/pipeworx-mcp-jira#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 83
- 2026-11-02: 68
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 81

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-jira
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-jira
- Repository: https://github.com/pipeworx-io/mcp-jira
- Website: https://pipeworx.io/packs/jira
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-jira/pipeworx-mcp-jira.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-jira/pipeworx-mcp-jira.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-jira/pipeworx-mcp-jira