Is MCP Jira Stdio safe to use?

MCP Jira Stdio has an HVTrust score of 74.2/100 (Grade B), ranked #239 of 1325 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 74.2/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 Model Context Protocol.

MCP Servers TypeScript Listed MIT

Is MCP Jira Stdio safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.5 / 10

Provenance Attested

Signed commits 78%

Last push 12d ago

Compare MCP Jira Stdio

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Jira Stdio scores 74.2/100 (Grade B), ranked #239 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.5/10; 78% of recent commits are signed; last pushed 2026-09-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Jira Stdio compares in MCP Servers

Bars show each HVTrust score; the tick marks MCP Jira Stdio’s 74.2.

Where the 74.2 comes from

HVTrust dimensions vs the MCP Servers average

74.2 / 100 · 100.0% confidence

MCP Jira Stdio MCP Servers average (775 agents)

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

17.0 / 25

6.7 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.3 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

15.2 / 20

3.1 above avg 12.1

AdoptionLog-scaled stars · package downloads

7.0 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.5/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

47.8

Activity sub-score · out of 100

#142

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 B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-14

12 days ago

Commits (4 wk)

Downloads (7d)

1,363

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #241

Analysis

Activity Inputs

47.8 / 100

StarsRepository reach

7.1 / 30

FreshnessLast push recency

23.3 / 25

ActivityRecent commits

12.5 / 25

CommunityFork signal

4.7 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

4.5 / 10

OpenSSF Scorecard · scanned Sep 23, 2026

Signed Commits

78%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 1

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

Common questions about MCP Jira Stdio

MCP Jira Stdio has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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.5/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?

Maintained. Last push was 12 days ago.

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

How this surface has changed

Detected changes to MCP Jira Stdio's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

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-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 713 spots (#956 → #243)

2026-09-23

HVTrust Changed

HVTrust up 48.2pts (25.7 → 73.9)

2026-09-22

Newly Listed

First tracked at rank #956

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-15

Rank Moved

Rank dropped 51 spots (#231 → #282)

2026-09-14

Rank Moved

Rank rose 40 spots (#271 → #231)

2026-09-12

Rank Moved

Rank rose 27 spots (#294 → #267)

2026-09-10

Rank Moved

Rank dropped 34 spots (#251 → #285)

2026-09-09

Rank Moved

Rank dropped 31 spots (#220 → #251)

2026-09-07

Grade Changed

Trust grade D → B

2026-09-07

Rank Moved

Rank rose 663 spots (#882 → #219)

2026-09-07

HVTrust Changed

HVTrust up 25.7pts (49.0 → 74.7)

2026-09-06

Rank Moved

Rank dropped 15 spots (#867 → #882)

2026-09-05

Rank Moved

Rank dropped 55 spots (#812 → #867)

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