Jira Tempo (huginnnx) MCP Server

@huginnnx/mcp-jira-tempo npm v1.0.2

Published by @huginnnx — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Jira Cloud (multi-profile) and Tempo Cloud: generic REST tools, file-based Jira profiles, and optional Tempo helpers for worklogs and accounts.

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 99 − adoption risk = 98/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:

PointsWhat was foundCategory
−1.2 Package runs install-time scripts MTC-SUP-010 supply-chain

2. Client adoption risk — 99 − 1 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

low Package runs install-time scripts (postinstall)MTC-SUP-010

"@huginnnx/mcp-jira-tempo" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.

Evidence: node scripts/ensure-executable.js

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package @huginnnx/mcp-jira-tempo

Tools 16

Each tool and what it can reach — statically extracted from the published source.

  • jira_deleteno sensitive capability
  • jira_getno sensitive capability
  • jira_patchno sensitive capability
  • jira_postno sensitive capability
  • jira_putno sensitive capability
  • tempo_deleteno sensitive capability
  • tempo_find_accounts_for_jira_projectno sensitive capability
  • tempo_getno sensitive capability
  • tempo_get_accountno sensitive capability
  • tempo_get_account_linksno sensitive capability
Show 6 more tools ↓
  • tempo_list_accountsno sensitive capability
  • tempo_list_work_attributesno sensitive capability
  • tempo_patchno sensitive capability
  • tempo_postno sensitive capability
  • tempo_putno sensitive capability
  • tempo_search_accountsno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.2 latest A 98/100 1 1.13.0 2026-09-08

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/huginnnx-mcp-jira-tempo/badge.svg)](https://mcptrustchecker.com/registry/huginnnx-mcp-jira-tempo)
HTML
<a href="https://mcptrustchecker.com/registry/huginnnx-mcp-jira-tempo"><img src="https://mcptrustchecker.com/registry/huginnnx-mcp-jira-tempo/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/huginnnx-mcp-jira-tempo/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @huginnnx/mcp-jira-tempo --online

Use the free API → How scoring works

Other implementations of Jira Tempo 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Productivity & Workflow