AtlassianJira MCP Integration Server (techrivers/AtlassianJira-MCP-Integration) is an MCP server listed on the M8ven Trust Index. It scores 41 out of 100, grade D. It declares 21 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
41/100

AtlassianJira MCP Integration Server

Enables Jira integration with dynamic configuration, time logging, task creation, issue updates, and bulk imports through natural language.

→ techrivers/AtlassianJira-MCP-Integration· 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

techrivers

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: 15 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: JIRA_API_TOKEN, JIRA_PROJECT_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes21 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.

getTimeline

Get timeline entries from Activity Timeline plugin with filtering options.

getResourceInfo

Get resource/user info from Activity Timeline plugin.

addTimeEntry

Add a new time entry to Activity Timeline for a specific issue.

updateTimeEntry

Update an existing time entry in Activity Timeline.

deleteTimeEntry

Delete a time entry from Activity Timeline.

getTimeEntryDetails

Get detailed information about a specific time entry.

getActivityTypes

Get available activity types for time entries.

getTimeReport

Generate time reports with filtering and export options.

bulkImportTimeEntries

Bulk import multiple time entries at once.

getJiraConfiguration

Get current Jira configuration status and settings (sensitive data masked).

updateJiraConfiguration

Update Jira configuration settings. Supports partial updates.

testJiraConnection

Test the current Jira configuration by making a connection to the API.

resetJiraConfiguration

Reset all Jira configuration settings. Requires confirmation.

suggestJiraConfiguration

Get intelligent suggestions for improving your Jira configuration.

startSecureConfiguration

Get instructions for secure Jira credential configuration (outside AI conversation).

checkSecureCredentials

Check the status of secure credential storage and get security recommendations.

createTask

Creates a new Jira issue/task.

logTime

Logs a work entry to a specific Jira issue.

meetingNotesToJira

Parse meeting notes and create Jira issues from action items. Supports both direct text input and file upload (.txt, .md, .rtf).

sheetToJiraStories

Create Jira issues from spreadsheet data. Supports Excel (.xlsx, .xls) and CSV files, plus Google Sheets links. Expected columns: Title/Summary (required), Description, Assignee, Priority, Type, Story Points, Labels. Use dryRun=true to preview first.

updateIssue

Updates an existing Jira issue with new field values, status transitions, and more.

// known CVEs in dependencies15 high5 medium10 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.17.3GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

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

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

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

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

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

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

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

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

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.
🔐 secretJIRA_API_TOKENYour Jira API token
configJIRA_DEFAULT_ASSIGNEEDefault assignee for new tasks
configJIRA_DEFAULT_PRIORITYDefault priority level
🔐 secretJIRA_PROJECT_KEYDefault project for task creation
configJIRA_URLYour Jira instance URL
configJIRA_USERNAMEYour Jira username/email
// 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

21/21 tools missing one or more hints — getTimeline (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); getResourceInfo (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); addTimeEntry (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +18 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

Only 0/5 tool handlers declare input schemas (0%)

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

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets not logged

1 secret value sent to log

Redact or omit secret values from log output.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Production dependencies are patched

0 critical, 15 high severity in production deps — @modelcontextprotocol/sdk@1.17.3 (high), @modelcontextprotocol/sdk@1.17.3 (high)

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

Dependency freshness

1/9 production deps stale: node-fetch@2023-11-30 (2.8y)

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/techrivers/atlassianjira-mcp-integration?variant=verified)](https://m8ven.ai/mcp/techrivers/atlassianjira-mcp-integration)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 05cf4eb8c76c99e8434ae849eafa126ebc1a535a
code hash: dafe1af9cfd2cc69066aa350b3b90c9dee84f7593e69bf79abf8d8f2a4209d74
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