MCP Atlassian (omkar9854/mcp-atlassian-onpremdc) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Limited view
69/100
20 days ago

MCP Atlassian

A Model Context Protocol server for Atlassian Jira and Confluence that supports both Cloud and On-Prem/Data Center deployments. It enables AI assistants to search, create, and manage issues and pages using secure authentication methods like PAT and OAuth.

→ omkar9854/mcp-atlassian-onpremdc· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

omkar9854

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

Glama

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

// key findings
✅
47 tools verified — handlers match their declared behaviour
26 read-only tools verified — handlers contain no write/delete/exec
✅
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 10 credentials: CONFLUENCE_API_TOKEN, CONFLUENCE_PERSONAL_TOKEN, JIRA_API_TOKEN, JIRA_PERSONAL_TOKEN, ATLASSIAN_OAUTH_CLIENT_SECRET, ATLASSIAN_OAUTH_ACCESS_TOKEN, CONFLUENCE_CLIENT_KEY, CONFLUENCE_CLIENT_KEY_PASSWORD, JIRA_CLIENT_KEY, JIRA_CLIENT_KEY_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configENABLED_TOOLS
configTRANSPORT
configHOST
configSTREAMABLE_HTTP_PATH
configCONFLUENCE_URL"": "https://your-company.atlassian.net/wiki",
configCONFLUENCE_USERNAME"": "your.email@company.com",
🔐 secretCONFLUENCE_API_TOKEN"": "your_api_token"
🔐 secretCONFLUENCE_PERSONAL_TOKENPAT auth: set JIRA_PERSONAL_TOKEN and
configJIRA_URL"": "https://your-company.atlassian.net",
configJIRA_USERNAME"": "your.email@company.com",
🔐 secretJIRA_API_TOKEN"": "your_api_token",
🔐 secretJIRA_PERSONAL_TOKENServer/Data Center users: Use instead of JIRA_USERNAME + JIRA_API_TOKEN. See [Authentication](https://personal-1d37018d.mintlify.app/docs/authentication) for details.
configATLASSIAN_OAUTH_CLIENT_ID
🔐 secretATLASSIAN_OAUTH_CLIENT_SECRET
configATLASSIAN_OAUTH_REDIRECT_URI
configATLASSIAN_OAUTH_SCOPE
configATLASSIAN_OAUTH_CLOUD_ID
🔐 secretATLASSIAN_OAUTH_ACCESS_TOKEN
configREAD_ONLY_MODE
configCONFLUENCE_SSL_VERIFYSSL: set JIRA_SSL_VERIFY=false or =false only when required
configCONFLUENCE_SPACES_FILTER
configJIRA_SSL_VERIFYSSL: set =false or CONFLUENCE_SSL_VERIFY=false only when required
configJIRA_PROJECTS_FILTER
configNO_PROXY
configATLASSIAN_OAUTH_ENABLE
configCONFLUENCE_HTTP_PROXY
configHTTP_PROXY
configCONFLUENCE_HTTPS_PROXY
configHTTPS_PROXY
configCONFLUENCE_NO_PROXY
configCONFLUENCE_SOCKS_PROXY
configSOCKS_PROXY
configCONFLUENCE_CLIENT_CERTClient certs: JIRA_CLIENT_CERT / JIRA_CLIENT_KEY and / CONFLUENCE_CLIENT_KEY
🔐 secretCONFLUENCE_CLIENT_KEYClient certs: JIRA_CLIENT_CERT / JIRA_CLIENT_KEY and CONFLUENCE_CLIENT_CERT /
🔐 secretCONFLUENCE_CLIENT_KEY_PASSWORD
configJIRA_HTTP_PROXY
configJIRA_HTTPS_PROXY
configJIRA_NO_PROXY
configJIRA_SOCKS_PROXY
configDISABLE_JIRA_MARKUP_TRANSLATION
configJIRA_CLIENT_CERTClient certs: / JIRA_CLIENT_KEY and CONFLUENCE_CLIENT_CERT / CONFLUENCE_CLIENT_KEY
🔐 secretJIRA_CLIENT_KEYClient certs: JIRA_CLIENT_CERT / and CONFLUENCE_CLIENT_CERT / CONFLUENCE_CLIENT_KEY
🔐 secretJIRA_CLIENT_KEY_PASSWORD
configMCP_LOG_FORMAT
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

All four hints declared on every tool

47/47 tools missing one or more hints — search (missing: destructiveHint, idempotentHint, openWorldHint); search_all (missing: destructiveHint, idempotentHint, openWorldHint); get_pages_bulk (missing: destructiveHint, idempotentHint, openWorldHint), +44 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 inputs are validated

46/47 tool handlers declare input schemas (98%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 11/47 tool handlers wrap calls in try/catch (23%)

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.

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 4 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/omkar9854-mcp-atlassian-onpremdc-zvrlet)](https://m8ven.ai/mcp/omkar9854-mcp-atlassian-onpremdc-zvrlet)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 286e670acb1815e5ee838b10c0507b697998e71d
code hash: 3b942796f879c80b508c2bfb23d46383a510a120327899d37aaea3cba3415975
verified: 8/7/2026, 2:42:53 AM
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