Emerging

74/100

6 days ago

mcp-atlassian

Item: mcp-atlassian
Rating: 74
Author: M8ven

Model Context Protocol (MCP) server for Atlassian Cloud products (Confluence and Jira). This integration is designed specifically for Atlassian Cloud instances and does not support Atlassian Server or Data Center deployments.

→ sooperset/mcp-atlassian · listed on modelscope

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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 push why connect →

Who stands behind it

sooperset

Source: modelscope · also listed on Official, mcp.so

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

modelscope GitHub mcp.so

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

// key findings

✅

98 tools verified — handlers match their declared behaviour

58 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 12 credentials: ATLASSIAN_OAUTH_CLIENT_SECRET, JIRA_OAUTH_CLIENT_SECRET, CONFLUENCE_OAUTH_CLIENT_SECRET, CONFLUENCE_API_TOKEN, CONFLUENCE_PERSONAL_TOKEN, JIRA_API_TOKEN, JIRA_PERSONAL_TOKEN, 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.

configATLASSIAN_OAUTH_ALLOWED_CLIENT_REDIRECT_URIS

configATLASSIAN_OAUTH_ALLOWED_GRANT_TYPES

configATLASSIAN_OAUTH_INSTANCE_URL

configJIRA_URL"": "https://your-company.atlassian.net",

configCONFLUENCE_URL"": "https://your-company.atlassian.net/wiki",

configATLASSIAN_OAUTH_CLIENT_ID

configJIRA_OAUTH_CLIENT_ID

configCONFLUENCE_OAUTH_CLIENT_ID

🔐 secretATLASSIAN_OAUTH_CLIENT_SECRET

🔐 secretJIRA_OAUTH_CLIENT_SECRET

🔐 secretCONFLUENCE_OAUTH_CLIENT_SECRET

configATLASSIAN_OAUTH_REDIRECT_URI

configATLASSIAN_OAUTH_SCOPE

configPUBLIC_BASE_URL

configHOST

configENABLED_TOOLS

configTOOLSETS

configTRANSPORT

configSTREAMABLE_HTTP_PATH

configCONFLUENCE_USERNAME"": "your.email@company.com",

🔐 secretCONFLUENCE_API_TOKEN"": "your_api_token"

🔐 secretCONFLUENCE_PERSONAL_TOKEN

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://mcp-atlassian.soomiles.com/docs/authentication) for details.

configATLASSIAN_OAUTH_CLOUD_ID

🔐 secretATLASSIAN_OAUTH_ACCESS_TOKEN

configREAD_ONLY_MODE

configCONFLUENCE_SSL_VERIFY

configCONFLUENCE_SPACES_FILTER

configJIRA_SSL_VERIFY

configJIRA_PROJECTS_FILTER

configNO_PROXY

configATLASSIAN_OAUTH_ENABLE

configCONFLUENCE_CLIENT_CERT

🔐 secretCONFLUENCE_CLIENT_KEY

🔐 secretCONFLUENCE_CLIENT_KEY_PASSWORD

configCONFLUENCE_TIMEOUT

configCONFLUENCE_ATTACHMENT_DOWNLOAD_USE_V1

configJIRA_SLA_METRICS

configJIRA_SLA_WORKING_HOURS_START

configJIRA_SLA_WORKING_HOURS_END

configJIRA_SLA_WORKING_DAYS

configJIRA_SLA_TIMEZONE

configJIRA_CLIENT_CERT

configJIRA_INTERNAL_ONLY_PROJECTS

configDISABLE_JIRA_MARKUP_TRANSLATION

🔐 secretJIRA_CLIENT_KEY

🔐 secretJIRA_CLIENT_KEY_PASSWORD

configJIRA_TIMEOUT

configHIERARCHY_LINK_PHRASES

configMCP_ATLASSIAN_VALIDATION_CACHE_TTL

configMCP_ATLASSIAN_VALIDATION_CACHE_MAXSIZE

configMCP_ALLOWED_URL_DOMAINS

configATLASSIAN_PROXY_WPAD_URL

configHTTP_PROXY

configHTTPS_PROXY

configSOCKS_PROXY

configno_proxy

Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.

deployPORT

// quality suggestions

All four hints declared on every tool

98/98 tools missing one or more hints — search (missing: destructiveHint, idempotentHint, openWorldHint); get_page (missing: destructiveHint, idempotentHint, openWorldHint); get_page_children (missing: destructiveHint, idempotentHint, openWorldHint), +95 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.

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 1 concrete improvement 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/sooperset-mcp-atlassian-6n0f5e)](https://m8ven.ai/mcp/sooperset-mcp-atlassian-6n0f5e)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: 556e7d4324cf360e195f5579a0cc4b8c959162e0

code hash: 9621a9726483b7ac4896ea1e70fa850a06438e702cafa3604fa9e8bb4172cf4c

verified: 8/13/2026, 10:50:32 PM

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