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

mcp-server-jira

Enables an AI agent to manage Jira Stories in a self-hosted Jira instance via the Jira REST API v2, including CRUD operations, workflow transitions, and burndown data retrieval.

→ sina-haseli/mcp-server-jira· 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
⚠️
Known vulnerabilities in dependencies: 14 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: JIRA_API_TOKEN, JIRA_PROJECT_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies14 high12 low

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

highaxios@1.6.0GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.6.0GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.6.0GHSA-43fc-jf86-j433

Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig

highaxios@1.6.0GHSA-4hjh-wcwx-xvwj

Axios is vulnerable to DoS attack through lack of data size check

highaxios@1.6.0GHSA-6chq-wfr3-2hj9

Axios: Header Injection via Prototype Pollution

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.
🔐 secretJIRA_API_TOKEN— ✅ API token / password used for Basic Auth
configJIRA_BASE_URL— ✅ Base URL of the Jira instance, e.g. https://jira.yourcompany.com
configJIRA_MCP_CONFIG
configJIRA_OUTLINE_LINK_FIELD— Custom field id for the Outline link (e.g. customfield_10100)
🔐 secretJIRA_PROJECT_KEY— ✅ Project key, e.g. PRD
configJIRA_STORY_ISSUE_TYPE— Issue type name for stories (default Story)
configJIRA_STORY_POINTS_FIELD— Custom field id for story points (default customfield_10016)
configJIRA_USER_EMAIL— ✅ Account email/username used for Basic Auth
// 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 2 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/sina-haseli-mcp-server-jira-1ho426)](https://m8ven.ai/mcp/sina-haseli-mcp-server-jira-1ho426)
commit: 61cdfa86622554c001a9448c95b36def72d8bf45
code hash: 75fa8c0433b57a9734460540fd9401345f8da91d4776a0e248fe41819af832cb
verified: 6/26/2026, 9:36:44 AM
view raw JSON →