Is MCP Jira Stdio safe to use?

MCP Jira Stdio has an HVTrust score of 49.0/100 (Grade D), ranked #796 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Jira Stdio?

MCP Jira Stdio scores 49.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 14 GitHub stars and is categorized under MCP Servers.

MCP Jira Stdio

freema/mcp-jira-stdio

MCP server for Jira integration with stdio transport. Issue management, project tracking, and workflow automation via Mo

MCP Servers TypeScript Grade D Listed MIT

49.0/100

Rank #796 of 1320

Compare MCP Jira Stdio

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-09-03 · 1d ago

Recent change

Rank +9

Is MCP Jira Stdio safe? MCP Jira Stdio scores 49.0/100 (Grade D), ranked #796 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.4/10; 78% of recent commits are signed; last pushed 2026-09-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#421 Atlassian Dc MCP — 49.1 (D) → #422 Dbmcp — 49.0 (D) → #424 Memory Journal MCP — 48.8 (D) → #425 MCP Server Infranodus — 48.8 (D) →

Quick Trust Read

What Would Improve It

Expose more independent signals, such as package metadata, provenance, or public usage evidence.

Recent Changes

2026-09-04

Rank Moved

Rank rose 24 spots (#820 → #796)

2026-09-03

Rank Moved

Rank dropped 33 spots (#787 → #820)

2026-09-02

Scorecard Added

OSSF Scorecard: 4.4/10

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.4/10. Tighten the weakest checks to improve public safety evidence.

Compare with another agent Get email alerts for MCP Jira Stdio View MCP Servers Report missing data

50.8

Activity sub-score · out of 100

#423

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

Forks

Last Push

2026-09-03

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲24

was #820

Analysis

HVTrust Dimensions vs MCP Servers

49.0 / 100 · 67.0% confidence

MCP Jira Stdio MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

16.9 / 25

7.4 above avg 9.5

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 11.8

Maintenance60% last-push freshness · 40% commit activity

16.5 / 20

4.3 above avg 12.2

AdoptionLog-scaled stars · package downloads

2.8 / 20

3.4 below avg 6.2

Activity Inputs

50.8 / 100

StarsRepository reach

7.1 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

14.3 / 25

CommunityFork signal

4.4 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

4.4 / 10

OpenSSF Scorecard · scanned Sep 2, 2026

Signed Commits

78%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 5

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is MCP Jira Stdio safe?

Public trust evidence for MCP Jira Stdio is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does MCP Jira Stdio publish package provenance?

Yes. MCP Jira Stdio's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does MCP Jira Stdio have an OpenSSF Scorecard?

MCP Jira Stdio has an OpenSSF Scorecard score of 4.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is MCP Jira Stdio actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does MCP Jira Stdio use?

MCP Jira Stdio ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Jira Stdio's commits signed?

78% of the last 100 commits to MCP Jira Stdio are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

MCP Jira Stdio appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain MCP Jira Stdio?

For maintainers

HVTrust scores MCP Jira Stdio from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-04

Rank Moved

Rank rose 24 spots (#820 → #796)

2026-09-03

Rank Moved

Rank dropped 33 spots (#787 → #820)

2026-09-02

Scorecard Added

OSSF Scorecard: 4.4/10

2026-09-02

Rank Moved

Rank rose 111 spots (#898 → #787)

2026-09-02

HVTrust Changed

HVTrust up 6.1pts (41.1 → 47.2)

2026-09-01

Rank Moved

Rank dropped 12 spots (#886 → #898)

2026-08-31

Rank Moved

Rank dropped 29 spots (#857 → #886)

2026-08-30

Rank Moved

Rank dropped 35 spots (#822 → #857)

2026-08-29

Rank Moved

Rank dropped 48 spots (#774 → #822)

2026-08-28

Rank Moved

Rank dropped 29 spots (#745 → #774)

2026-08-27

Rank Moved

Rank dropped 21 spots (#724 → #745)

2026-08-26

Rank Moved

Rank dropped 100 spots (#624 → #724)

2026-08-16

Rank Moved

Rank dropped 11 spots (#600 → #611)

2026-08-08

Newly Listed

First tracked at rank #586

GitHub → npm: mcp-jira-stdio

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-jira-stdio.svg)](https://hvtracker.net/agents/mcp-jira-stdio)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-jira-stdio"><img src="https://hvtracker.net/badge/mcp-jira-stdio.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON