Back to MCP Trust Indexm8ven
D
Caution
50/100
2 months ago

mcp-jira-tempo

A Jira and Tempo Cloud MCP server with file-based profiles for multi-site access, enabling natural language interaction with issue tracking, project management, and Tempo worklogs via generic REST tools.

→ huginnnx/mcp-jira-tempo· 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

huginnnx

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
⚠️
Known vulnerabilities in dependencies: 3 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.
🔐
You'll be asked for 1 credential: ATLASSIAN_API_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies3 high

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

high@modelcontextprotocol/sdk@1.23.0GHSA-345p-7cg4-v4c7

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

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

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

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

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

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.
🔐 secretATLASSIAN_API_TOKENBackward compatibility: legacy single-site ATLASSIAN_SITE_NAME, ATLASSIAN_USER_EMAIL, and still work for quick tests or simple setups.
configATLASSIAN_DEFAULT_PROFILEDeterministic profile resolution: explicit profile, then , then file defaultProfile, then legacy single-site credentials.
configATLASSIAN_PROFILES_FILEFile-based Jira profiles: prefer for named multi-site Jira access.
configATLASSIAN_PROFILES_JSONis no longer supported for Jira profiles. Migrate profile-based setups to ATLASSIAN_PROFILES_FILE.
configATLASSIAN_SITE_NAMEBackward compatibility: legacy single-site , ATLASSIAN_USER_EMAIL, and ATLASSIAN_API_TOKEN still work for quick tests or simple setups.
configATLASSIAN_USER_EMAILBackward compatibility: legacy single-site ATLASSIAN_SITE_NAME, , and ATLASSIAN_API_TOKEN still work for quick tests or simple setups.
configPACKAGE_NAME
configTRANSPORT_MODE
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

16/16 tools missing one or more hints — jira_get (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jira_post (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jira_put (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +13 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

Only 0/16 tools referenced in tests (0%)

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

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, 3 high severity in production deps — @modelcontextprotocol/sdk@1.23.0 (high), @modelcontextprotocol/sdk@1.23.0 (high)

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

Dependency freshness

1/9 production deps stale: jmespath@2022-06-19 (4y)

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 6 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/huginnnx-mcp-jira-tempo-1lssto?variant=verified)](https://m8ven.ai/mcp/huginnnx-mcp-jira-tempo-1lssto)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 3f21d97e5308085f16a8b11e1fa06577412a5253
code hash: 5bac5315622ab9e98b28a9359d20c1ffc5ce74d372bce4ce5e1c1f20a181759e
verified: 6/21/2026, 10:19:19 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