Is Atlassian Rovo MCP Server safe to use?

Atlassian Rovo MCP Server has an HVTrust score of 60.5/100 (Grade C), ranked #450 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Atlassian Rovo MCP Server?

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

Atlassian Rovo MCP Server

atlassian/atlassian-mcp-server

Official remote MCP server for Atlassian. Securely connect Jira, Confluence, Jira Service Management, Bitbucket, and Com

MCP Servers JavaScript Grade C Listed Apache-2.0

60.5/100

Rank #450 of 1320

Compare Atlassian Rovo MCP Server

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 C · 2/5 signals

Last push

2026-09-03 · 1d ago

Recent change

Rank +8

Is Atlassian Rovo MCP Server safe? Atlassian Rovo MCP Server scores 60.5/100 (Grade C), ranked #450 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.7/10; 39% 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

#210 Vibe Check MCP Server — 60.7 (C) → #211 Lumino MCP Server — 60.6 (C) → #213 Prometheus MCP — 60.4 (C) → #214 Cloudflare MCP Server — 60.3 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-04

Rank Moved

Rank dropped 15 spots (#435 → #450)

2026-09-03

Rank Moved

Rank rose 42 spots (#477 → #435)

2026-08-31

Rank Moved

Rank dropped 32 spots (#440 → #472)

Maintainer Checklist

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

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

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

68.0

Activity sub-score · out of 100

#212

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

1.0k

Forks

127

Last Push

2026-09-03

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼15

was #435

Analysis

HVTrust Dimensions vs MCP Servers

60.5 / 100 · 100.0% confidence

Atlassian Rovo MCP Server MCP Servers average (778 agents)

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

10.3 / 25

0.7 above avg 9.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.2 / 17

2.4 above avg 11.8

Maintenance60% last-push freshness · 40% commit activity

16.8 / 20

4.6 above avg 12.2

AdoptionLog-scaled stars · package downloads

7.2 / 20

0.9 above avg 6.3

Activity Inputs

68.0 / 100

StarsRepository reach

18.0 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

15.3 / 25

CommunityFork signal

9.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.7 / 10

OpenSSF Scorecard · scanned Aug 30, 2026

Signed Commits

39%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 4

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies -1

SAST 3

Security-Policy 10

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 10

Is Atlassian Rovo MCP Server safe?

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

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

Does Atlassian Rovo MCP Server have an OpenSSF Scorecard?

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

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

What license does Atlassian Rovo MCP Server use?

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

Are Atlassian Rovo MCP Server's commits signed?

39% of the last 100 commits to Atlassian Rovo MCP Server 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

Atlassian Rovo MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

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 Atlassian Rovo MCP Server'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-12

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

Maintain Atlassian Rovo MCP Server?

For maintainers

HVTrust scores Atlassian Rovo MCP Server 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 dropped 15 spots (#435 → #450)

2026-09-03

Rank Moved

Rank rose 42 spots (#477 → #435)

2026-08-31

Rank Moved

Rank dropped 32 spots (#440 → #472)

2026-08-30

Rank Moved

Rank rose 10 spots (#450 → #440)

2026-08-29

Scorecard Added

OSSF Scorecard: 6.7/10

2026-08-29

Grade Changed

Trust grade D → C

2026-08-29

Rank Moved

Rank rose 644 spots (#1094 → #450)

2026-08-29

HVTrust Changed

HVTrust up 35.1pts (22.2 → 57.3)

2026-08-28

Rank Moved

Rank dropped 28 spots (#1066 → #1094)

2026-08-27

Rank Moved

Rank dropped 23 spots (#1043 → #1066)

2026-08-26

Rank Moved

Rank dropped 83 spots (#960 → #1043)

2026-08-25

Rank Moved

Rank dropped 48 spots (#912 → #960)

2026-08-24

Rank Moved

Rank rose 80 spots (#992 → #912)

2026-08-24

Activity Score Changed

Activity score up 9pts (55 → 64)

2026-08-17

Rank Moved

Rank rose 12 spots (#1004 → #992)

2026-08-16

Rank Moved

Rank dropped 30 spots (#974 → #1004)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

2026-08-12

Rank Moved

Rank rose 43 spots (#1007 → #964)

2026-08-10

Rank Moved

Rank dropped 57 spots (#943 → #1000)

2026-08-08

Newly Listed

First tracked at rank #897

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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