jiraxmcp (vaibhavpandeyvpz/jiraxmcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
2 months ago

jiraxmcp

An MCP server for interacting with Jira Cloud, providing tools for issues, search, agile boards, comments, links, attachments, and webhook notifications.

→ vaibhavpandeyvpz/jiraxmcp· listed on glama

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 pushwhy connect →

Who stands behind it

vaibhavpandeyvpz

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.
✅
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 3 credentials: JIRA_ACCESS_TOKEN, JIRA_API_TOKEN, JIRA_WEBHOOK_SECRET
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.
🔐 secretJIRA_ACCESS_TOKENSupports either or JIRA_EMAIL plus JIRA_API_TOKEN.
🔐 secretJIRA_API_TOKENSupports either JIRA_ACCESS_TOKEN or JIRA_EMAIL plus .
configJIRA_EMAILSupports either JIRA_ACCESS_TOKEN or plus JIRA_API_TOKEN.
configJIRA_HOSTJira Cloud base URL exported as
configJIRA_WEBHOOK_HOSTJIRA_WEBHOOK_PORT overrides the default listener port 6543. controls the bind host and defaults to 127.0.0.1.
configJIRA_WEBHOOK_PORToverrides the default listener port 6543. JIRA_WEBHOOK_HOST controls the bind host and defaults to 127.0.0.1.
🔐 secretJIRA_WEBHOOK_SECRETIf you configure a webhook secret in Jira admin webhooks, also set so incoming X-Hub-Signature headers are verified before events are emitted.
// 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

31/31 tools missing one or more hints — jira_get_issue (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jira_create_issue (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jira_update_issue (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +28 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

30/31 tool handlers declare input schemas (97%)

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

Tool handlers catch errors

Only 0/31 tool handlers wrap calls in try/catch (0%)

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 5 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/vaibhavpandeyvpz-jiraxmcp-q5jxvx)](https://m8ven.ai/mcp/vaibhavpandeyvpz-jiraxmcp-q5jxvx)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 4e453e67a6d5839a80b50e3708fa2a625e2b8839
code hash: 070faca259da392018d43b22fe5869b6c67ffb73c5d62abfc48dce2f3d0e469f
verified: 6/14/2026, 10:18:20 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