jira-mcp (nayzo/jira-mcp) is an MCP server listed on the M8ven Trust Index. It scores 66 out of 100, grade C. It declares 29 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
66/100

jira-mcp

MCP server for Jira Cloud tailored for ALM projects with Zephyr Scale integration, enabling issue management, sprint tracking, and test step operations.

→ nayzo/jira-mcp· listed on glama

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

Code 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

nayzo

Source: Glama

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

Glamanot 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: ZAPI_ACCESS_KEY. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 5 credentials: JIRA_API_TOKEN, JIRA_PROJECT_KEY, TICKET_KEY, ZAPI_ACCESS_KEY, ZAPI_SECRET_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 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.7.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.7.0GHSA-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.
configAUTO_CREATE_TEST_TICKETSAuto-create Test ticket when a Story has points (default: true)
configJIRA_ACCEPTANCE_CRITERIA_FIELD
configJIRA_ALTERNATE_CATEGORY_ID
configJIRA_ALTERNATE_CATEGORY_VALUE
🔐 secretJIRA_API_TOKEN✅ API token from [id.atlassian.com](https://id.atlassian.com/manage-profile/security/api-tokens)
configJIRA_CATEGORY_FIELD
configJIRA_CRISIS_FIELD
configJIRA_CRISIS_NO_ID
configJIRA_CRISIS_YES_ID
configJIRA_DEFAULT_ASSIGNEE_ACCOUNT_ID
configJIRA_DEFAULT_CATEGORY_ID
configJIRA_DEFAULT_CATEGORY_VALUE
configJIRA_EPIC_LINK_FIELD
configJIRA_HOST✅ e.g. your-company.atlassian.net
configJIRA_PRODUCT_FIELD
configJIRA_PRODUCT_ID
configJIRA_PRODUCT_VALUE
🔐 secretJIRA_PROJECT_KEY✅ e.g. ALM
configJIRA_STORY_POINTS_FIELD
configJIRA_STORY_READINESS_FIELD
configJIRA_STORY_READINESS_NO_ID
configJIRA_STORY_READINESS_YES_ID
configJIRA_USERNAME✅ Your Atlassian email
🔐 secretTICKET_KEY
configUSE_ALTERNATE_CATEGORY
🔐 secretZAPI_ACCESS_KEY
configZAPI_ACCOUNT_ID
configZAPI_BASE_URL
🔐 secretZAPI_SECRET_KEY
// 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

29/29 tools missing one or more hints — create-ticket (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); link-tickets (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get-ticket (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +26 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.

Tool handlers catch errors

Only 11/29 tool handlers wrap calls in try/catch (38%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

1 child_process call — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets not logged

2 secret values sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 2 high severity in production deps — @modelcontextprotocol/sdk@1.7.0 (high), @modelcontextprotocol/sdk@1.7.0 (high)

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

Dependency freshness

2/7 production deps stale: crypto@2022-06-14 (4y), node-fetch@2023-11-30 (2.6y)

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 7 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/nayzo/jira-mcp?variant=verified)](https://m8ven.ai/mcp/nayzo/jira-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: ba2769cd3548b244a92c06ded56d5409d275472e
code hash: 168f442e2409df56c4acd6eaa2d64e2aded9c291c48153adefde83b9136e51bd
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