Is MCP Atlassian safe to use?

MCP Atlassian has an HVTrust score of 72.1/100 (Grade B), ranked #110 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Atlassian?

MCP Atlassian scores 72.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 5.7k GitHub stars and is categorized under MCP Servers.

MCP Atlassian

sooperset/mcp-atlassian

MCP server for Atlassian tools (Confluence, Jira)

MCP Servers Python Grade B Listed MIT

72.1/100

Rank #110 of 1204

Compare MCP Atlassian

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-08 · 1d ago

Recent change

Provider Removed

Is MCP Atlassian safe? MCP Atlassian scores 72.1/100 (Grade B), ranked #110 of 1204 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.3/10; 100% of recent commits are signed; last pushed 2026-08-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#15 ARC-1 — 72.9 (B) → #16 Blockrun MCP — 72.5 (B) → #18 Touchdesigner MCP — 72.0 (B) → #19 Safari MCP — 71.9 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Anthropic

2026-07-13

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

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

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

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

84.6

Activity sub-score · out of 100

#17

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 →

Activity & Reach

Stars

5.7k

Forks

1.3k

Last Push

2026-08-08

yesterday

Commits (4 wk)

Downloads (7d)

388,517

pypi

HN mentions (30d)

—

Open Issues

130

Rank Change

▼3

was #107

Analysis

HVTrust Dimensions vs MCP Servers

72.1 / 100 · 100.0% confidence

MCP Atlassian MCP Servers average (718 agents)

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

11.6 / 25

6.5 above avg 5.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

13.0 / 17

4.2 above avg 8.8

Maintenance60% last-push freshness · 40% commit activity

19.2 / 20

6.7 above avg 12.5

AdoptionLog-scaled stars · package downloads

16.5 / 20

11.0 above avg 5.5

Activity Inputs

84.6 / 100

StarsRepository reach

22.5 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

22.7 / 25

CommunityFork signal

14.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.3 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 7

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is MCP Atlassian safe?

MCP Atlassian 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 Atlassian publish package provenance?

No published build provenance is currently detected for MCP Atlassian. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MCP Atlassian have an OpenSSF Scorecard?

MCP Atlassian has an OpenSSF Scorecard score of 5.3/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 Atlassian actively maintained?

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

What license does MCP Atlassian use?

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

Are MCP Atlassian's commits signed?

100% of the last 100 commits to MCP Atlassian 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 Atlassian appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

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 Atlassian'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-08-07

Provider Removed

Runtime surface shrank — no longer detected: Anthropic

2026-07-13

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Activity Resumed

Activity resumed

Maintain MCP Atlassian?

For maintainers

HVTrust scores MCP Atlassian 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-08-07

Provider Removed

Runtime surface shrank — no longer detected: Anthropic

2026-07-13

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Activity Resumed

Activity resumed

2026-07-13

Grade Changed

Trust grade D → B

2026-07-13

Rank Moved

Rank rose 264 spots (#336 → #72)

2026-07-13

HVTrust Changed

HVTrust up 64.0pts (10.1 → 74.1)

2026-07-13

Activity Score Changed

Activity score up 87pts (0 → 87)

2026-07-12

Newly Listed

First tracked at rank #336

GitHub → PyPI: mcp-atlassian

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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