A

npm:@atlassian-dc-mcp/jira

https://www.npmjs.com/package/@atlassian-dc-mcp/jira
93/100 · MCP Trust Grade · checked 24d ago · MCP 0.29.0

Is the npm:@atlassian-dc-mcp/jira MCP server safe to use?

Independent trust grade A (93/100). Static analysis of npm package @atlassian-dc-mcp/jira@0.29.0 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured. wmcp.sh continuously watches npm:@atlassian-dc-mcp/jira for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

What it offers — 14 tools · Developer Tools

jira_searchIssues

Search for JIRA issues using JQL in the ${jiraInstanceType}

jira_getIssue

Get details of a JIRA issue by its key from the ${jiraInstanceType}

jira_getIssueComments

Get comments of a JIRA issue by its key from the ${jiraInstanceType}

jira_createIssue

Create a new JIRA issue in the ${jiraInstanceType}

jira_updateIssue

Update an existing JIRA issue in the ${jiraInstanceType}

jira_postIssueComment

Post a comment on a JIRA issue in the ${jiraInstanceType}

jira_getTransitions

Get available status transitions for a JIRA issue in the ${jiraInstanceType}. Returns a list of transitions with their IDs, names, and target statuses

jira_getIssueDevelopmentInfo

Get linked development information (pull requests, commits, or branches) shown in the Development panel of a JIRA issue in the ${jiraInstanceType}. De

jira_transitionIssue

Transition a JIRA issue to a new status in the ${jiraInstanceType}. Use jira_getTransitions first to get available transition IDs.

jira_getIssueLinkTypes

Get the list of available issue link types (e.g. Blocks, Relates, Duplicate) in the ${jiraInstanceType}. Use this to discover valid link type names be

jira_linkIssues

Create a link between two JIRA issues in the ${jiraInstanceType}. Use jira_getIssueLinkTypes to find valid link type names.

jira_unlinkIssues

Delete an existing link between two JIRA issues in the ${jiraInstanceType}. Requires the issue link id (found in the

jira_uploadAttachment

Upload a local file as an attachment to a JIRA issue in the ${jiraInstanceType}. The file must live under the server-configured upload directory; the

jira_downloadAttachment

Download attachment(s) from a JIRA issue in the ${jiraInstanceType}, by issue key (optionally filtered by filename) or by a single attachment id. Retu

Spec / packaging20%100
Security (OWASP MCP)30%90
Maintenance / popularity20%100
Tool hygiene15%95
Transparency / provenance15%75

Findings

INFO Static analysis of npm package @atlassian-dc-mcp/jira@0.29.0 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:@atlassian-dc-mcp/jira on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:@atlassian-dc-mcp/jira grade A
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade A · wmcp.sh
[![MCP Trust Grade A](https://wmcp.sh/mcp/grade/npm%3A%40atlassian-dc-mcp%2Fjira/badge.svg)](https://wmcp.sh/mcp/grade/npm%3A%40atlassian-dc-mcp%2Fjira)
<a href="https://wmcp.sh/mcp/grade/npm%3A%40atlassian-dc-mcp%2Fjira"><img src="https://wmcp.sh/mcp/grade/npm%3A%40atlassian-dc-mcp%2Fjira/badge.svg" alt="MCP Trust Grade A · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.