JIRA MCP Server (rixbeck/jira-mcp) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 15 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
56/100

JIRA MCP Server

MCP server for self-hosted Jira

→ rixbeck/jira-mcp· listed on mcp_so

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Sandbox Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

rixbeck

Source: mcp.so

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

mcp.sonot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: JIRA_PASSWORD. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 2 credentials: JIRA_ACCESS_TOKEN, JIRA_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes15 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

getProjects

Get list of JIRA projects

getTasks

Get JIRA tasks based on JQL query

getTask

Get a single JIRA task by ID

updateTask

Update fields of a JIRA task, optionally including its status. Only the given fields change.

updateTaskStatus

Update the status of a JIRA task (see also updateTask, which can change status together with other fields)

updateTaskOwner

Update the assignee of a JIRA task

getTaskAttachments

Get list of attachments for a JIRA task

downloadTaskAttachment

Download a specific attachment from a JIRA task by filename

downloadTaskAttachments

Download all attachments from a JIRA task to a specified directory

getAvailableStatuses

Get list of available JIRA statuses for a task

createTask

Create a new JIRA task (issue)

addTaskComment

Add a comment to a JIRA task

getTaskComments

Get all comments for a JIRA task

getProjectUsers

Get list of available users under a specific JIRA project

addAttachment

Add an attachment to a JIRA task

// known CVEs in dependencies3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.10.1GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.10.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.10.1GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretJIRA_ACCESS_TOKEN
configJIRA_HOST
🔐 secretJIRA_PASSWORD
configJIRA_USERNAME
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

15/15 tools missing one or more hints — getProjects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); getTasks (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); getTask (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +12 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets not written to files

2 secret values written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.10.1 (high), @modelcontextprotocol/sdk@1.10.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/rixbeck/jira-mcp?variant=verified)](https://m8ven.ai/mcp/rixbeck/jira-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 2f46b7d3bb46d3f35e130142d0e1a9bff2322dc5
code hash: 45cf4237db0b11c01562528c26842196ec2f017f1c042208dd70955a7c3b9c47
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client