TarasKhust/jira-mcp-server (TarasKhust/jira-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 54 out of 100, grade D. It declares 37 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
54/100

TarasKhust/jira-mcp-server

MCP server for Jira and Confluence integration with 32 tools for managing tickets, sprints, boards, worklogs, and Confluence pages.

→ TarasKhust/jira-mcp-server· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. 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

TarasKhust

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
⚠️
Known vulnerabilities in dependencies: 16 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
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 2 credentials: CONFLUENCE_API_TOKEN, JIRA_API_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes37 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

get_agile_boards

Get all Agile boards for a project

get_board_issues

Get issues from an Agile board

get_sprints_from_board

Get all sprints from an Agile board

get_sprint_issues

Get issues from a sprint

batch_create_issues

Create multiple Jira issues in a batch

get_comments

Get comments for a specific Jira ticket

add_comment

Add a comment to a Jira ticket. Supports mentions using [~accountId] or [~email@example.com] format.

delete_comment

Delete a comment from a Jira ticket

delete_all_comments

Delete all comments from a Jira ticket

get_kb_page

Get a Confluence/KB page by page ID or full URL. Returns page title, space, content (as plain text), version, and metadata.

search_kb_pages

Search for Confluence/KB pages by text, title, or CQL query. Returns matching pages with titles, spaces, and URLs.

get_kb_page_children

Get child pages of a Confluence/KB page. Useful for navigating page hierarchies.

get_kb_page_comments

Get comments on a Confluence/KB page

get_kb_spaces

List available Confluence/KB spaces. Useful for discovering space keys before searching.

update_ticket_fields

Update fields of a Jira ticket (e.g., original estimate, story points, labels, assignee, priority, due date, etc.)

get_ticket_fields

Get all available fields and their metadata for a Jira ticket (useful for finding custom field IDs)

get_available_fields

Get all available fields for a Jira ticket with their metadata and field IDs. Returns a mapping of field names to field IDs that can be used in update_ticket_fields.

create_issue_link

Create a link between two Jira issues

remove_issue_link

Remove a link between two Jira issues

get_all_projects

Get all Jira projects

get_project_issues

Get all issues for a specific project

get_project_versions

Get all versions for a project

create_version

Create a new version in a project

list_tickets

List Jira tickets assigned to you

get_ticket

Get details of a specific Jira ticket

create_ticket

Create a new Jira ticket

search_tickets

Search for tickets in specific projects using text search

delete_issue

Delete a Jira ticket

search_users

Search for Jira users by email or display name to get their accountId for mentions

get_user_profile

Get user profile information

update_status

Update the status of a Jira ticket

get_transitions

Get available transitions for a Jira ticket

assign_ticket

Assign a Jira ticket to a user

add_worklog

Add worklog (time spent) to a Jira ticket

get_worklog

Get worklogs for a specific Jira ticket

update_worklog

Update an existing worklog on a Jira ticket

delete_worklog

Delete a worklog from a Jira ticket

// known CVEs in dependencies16 high12 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.7.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.7.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highaxios@1.8.0GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.8.0GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.8.0GHSA-43fc-jf86-j433

Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
🔐 secretCONFLUENCE_API_TOKENyour-api-token
configCONFLUENCE_EMAILyour-email@example.com
configCONFLUENCE_HOST
🔐 secretJIRA_API_TOKENyour-api-token
configJIRA_EMAILyour-email@example.com
configJIRA_HOST"": "https://your-domain.atlassian.net",
// 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

37/37 tools missing one or more hints — get_agile_boards (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_board_issues (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_sprints_from_board (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +34 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

35/37 tool handlers declare input schemas (95%)

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

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

1 child_process call — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 16 high severity in production deps — @modelcontextprotocol/sdk@1.7.0 (high), @modelcontextprotocol/sdk@1.7.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Domain consistency

npm scope @tarasrushchak doesn't match GitHub owner taraskhust

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 7 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 Verified](https://m8ven.ai/badge/mcp/taraskhust/jira-mcp-server?variant=verified)](https://m8ven.ai/mcp/taraskhust/jira-mcp-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 27b2f018e8975e2c2679384b065513b350ff2f1e
code hash: fbe655c5f8d90b9fcf070129af159bd6431ddca309a6d1896bc081b7acf930b6
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