74
/ 100
10 days ago
glama
Jira Product Discovery MCP
Exposes generic Jira REST tools and native Jira Product Discovery operations for Jira Cloud, including insights and attachments.
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
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
// key findings
✅
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: ATLASSIAN_API_TOKEN, ATLASSIAN_OAUTH_BEARER
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// required environment variables
This server reads these from
process.env. You'll be asked to provide them before it can run.🔐 secret
ATLASSIAN_API_TOKEN— api-token>config
ATLASSIAN_CLOUD_ID— Set when the bearer can access more than one Atlassian🔐 secret
ATLASSIAN_OAUTH_BEARER— access-token> \config
ATLASSIAN_SITE_NAME— your-instanceconfig
ATLASSIAN_USER_EMAIL— you@example.comconfig
PACKAGE_NAMEconfig
PORTconfig
TRANSPORT_MODE// 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 3 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
[](https://m8ven.ai/mcp/aavaz-ai-jira-product-discovery-mcp-1jt0k2)commit: f39fbe0a9c65b0fe312aeb8f1ab1fc142db6df99
code hash: 052f9886579a2831bebf147c54a656444f271336767628ebff541c9645e6a166
verified: 7/21/2026, 9:21:55 AM