Back to MCP Trust Indexm8ven
68
/ 100
1 month ago
glama

JIRA MCP

A Model Context Protocol server for integrating JIRA with Claude, enabling AI assistants to create, search, update, and link JIRA tickets, as well as manage Zephyr test steps through natural language.

→ MankowskiNick/jira-mcp· listed on 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.

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
3 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 →
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configAUTO_CREATE_TEST_TICKETS— "": "true",
configJIRA_ACCEPTANCE_CRITERIA_FIELD— "": "customfield_10429",
configJIRA_ALTERNATE_CATEGORY_ID— "": "67890"
configJIRA_ALTERNATE_CATEGORY_VALUE— "": "Alternate Category",
🔐 secretJIRA_API_TOKEN— "": "your_api_token",
configJIRA_CATEGORY_FIELD— "": "customfield_10636",
configJIRA_CRISIS_FIELD— The field ID for the crisis field (default: "customfield_10597")
configJIRA_CRISIS_NO_ID— The ID of the "No" option (default: "18259")
configJIRA_CRISIS_YES_ID— The ID of the "Yes" option (default: "18258")
configJIRA_DEFAULT_CATEGORY_ID— "": "12345",
configJIRA_DEFAULT_CATEGORY_VALUE— "": "Default Category",
configJIRA_EPIC_LINK_FIELD— "": "customfield_10014",
configJIRA_HOST— "": "your-site.atlassian.net",
configJIRA_PRODUCT_FIELD— "": "customfield_10757",
configJIRA_PRODUCT_ID— "": "12345",
configJIRA_PRODUCT_VALUE— "": "Your Product Name",
🔐 secretJIRA_PROJECT_KEY— "": "your_project_key",
configJIRA_STORY_POINTS_FIELD— "": "customfield_10040",
configJIRA_USERNAME— "": "your-email@example.com",
🔐 secretTICKET_KEY
configUSE_ALTERNATE_CATEGORY— "": "false",
🔐 secretZAPI_ACCESS_KEY— Your Zephyr Access Key (found in Zephyr Cloud settings under API Keys)
configZAPI_ACCOUNT_ID
configZAPI_BASE_URL— The base URL for the Zephyr API (default: "https://prod-api.zephyr4jiracloud.com/connect")
🔐 secretZAPI_SECRET_KEY— Your Zephyr Secret Key (found in Zephyr Cloud settings under API Keys)
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// 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 Score](https://m8ven.ai/badge/mcp/mankowskinick-jira-mcp-ud6uhi)](https://m8ven.ai/mcp/mankowskinick-jira-mcp-ud6uhi)
commit: fd5a0aa01207d656d86e39b2d33a638ee7d5fa6e
code hash: 76c1b9d28c9be6da16782a9c45c4397d4812a9a5f1b411f96a75562e8993c1ce
verified: 6/17/2026, 11:38:00 AM
view raw JSON →