claude-mcp-jira (zcc-cddg-mx/claude-mcp-jira) is an MCP server listed on the M8ven Trust Index. It scores 71 out of 100, grade C. It declares 8 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
71/100
2 months ago

claude-mcp-jira

Integrates Claude with Jira for corporate environments using an internal MCP server with SSE, supporting ticket creation, update, summarization, and listing via natural language commands.

→ zcc-cddg-mx/claude-mcp-jira· 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

zcc-cddg-mx

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
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 2 credentials: MCP_API_KEY, JIRA_PROJECT_KEY
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.
configSERVICE_URL
configJIRA_CLI_USER
🔐 secretMCP_API_KEYcp .env.example .env # completar JIRA_PAT y
configMCP_ALLOWED_CIDRS
configMCP_RATE_LIMIT_MAX_CALLS
configMCP_RATE_LIMIT_WINDOW
configMCP_KEY_ROLES
configMCP_DEFAULT_ROLE
configAUDIT_LOG_PATH
configMCP_MAX_PAYLOAD_SIZE
configJIRA_MAX_RESULTS
configMCP_SSE_TIMEOUT
configMCP_PORT
configMCP_SERVICE_TIMEOUT
configAUDIT_LOG_MAX_BYTES
configAUDIT_LOG_BACKUP_COUNT
configANTHROPIC_MODEL
configTICKET_LANGProyecto JIRA_PROJECT_KEY Propósito
configJIRA_URL
configJIRA_PATcp .env.example .env # completar y MCP_API_KEY
🔐 secretJIRA_PROJECT_KEYProyecto TICKET_LANG Propósito
configREQUESTS_CA_BUNDLEEn .env, apunta al cert del endpoint que se va a llamar. Ver .env.example para detalles.
configJIRA_TIMEOUT
configRATE_LIMIT_MAX_CALLS
configRATE_LIMIT_WINDOW
configAPP_ENV
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

8/8 tools missing one or more hints — create_jira_issue (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); update_jira_issue (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_jira_issue (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

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/zcc-cddg-mx/claude-mcp-jira)](https://m8ven.ai/mcp/zcc-cddg-mx/claude-mcp-jira)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 041332b24b7c1f6972838bec2c3aa9c4cf35dcee
code hash: ed80303d3576b1a59926155849509634f73d26c97315b948b29a11ea99b8f31c
verified: 6/20/2026, 9:10:35 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