Jira Agent Gateway (yauchinlam/jira-agent-gateway) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 15 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
24 days ago

Jira Agent Gateway

A secure, TypeScript-based MCP gateway that enables AI agents to interact with Jira through controlled, audited tool calls without exposing credentials.

→ yauchinlam/jira-agent-gateway· 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

yauchinlam

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

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// 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: JIRA_API_TOKEN, JIRA_OAUTH_ACCESS_TOKEN
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.
configJIRA_ALLOW_ISSUE_DELETES
🔐 secretJIRA_API_TOKENreplace-me
configJIRA_APPROVAL_MODEUse console for local development, webhook for production approval workflows, or none to deny approval-gated actions.
configJIRA_AUDIT_LOG_FILE
configJIRA_AUDIT_LOG_MODEUse console for local development, file for local append-only logs, webhook for centralized audit ingestion, or none to disable audit logging.
configJIRA_AUTH_MODEUse scoped by default. Use classic only for quick local development, prototyping, or compatibility fallback.
configJIRA_BASE_URLUse your Jira site URL, usually https://your-company.atlassian.net. Open Jira in your browser and copy the origin before /jira or /browse.
configJIRA_CLOUD_ID
configJIRA_DEFAULT_PROJECTUse the Jira project key shown in issue keys, such as PROJ from PROJ-123.
configJIRA_DEPLOYMENT_TYPE
configJIRA_EMAILAssignment defaults: whenever a tool has an assignee option and the caller omits it, the gateway assigns work to the Jira account configured by .
configJIRA_MAX_SEARCH_RESULTS
🔐 secretJIRA_OAUTH_ACCESS_TOKEN
configJIRA_REQUIRE_APPROVAL_FOR_HIGH_RISK
configJIRA_WEBHOOK_APPROVAL_URL
configJIRA_WEBHOOK_AUDIT_URL
// 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

15/15 tools missing one or more hints — add_jira_comment (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); add_jira_issues_to_sprint (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); assign_jira_issue (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +12 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.).

Tool test coverage

8/15 tools referenced in tests (53%)

Write tests that reference each tool by name so every tool has at least one test.

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/yauchinlam/jira-agent-gateway)](https://m8ven.ai/mcp/yauchinlam/jira-agent-gateway)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 5190d45b75f51c01696fbbe173db873ae59f864c
code hash: 447962dd1b8fdf5f2a1ea84124c8777e850faeae8df1220f3c967ef50665dca0
verified: 8/19/2026, 3:08:12 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