Is Atlassian Rovo MCP Server safe to use?

Atlassian Rovo MCP Server has an HVTrust score of 61.1/100 (Grade C), ranked #602 of 1325 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 61.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.1k 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 Compass to Claude, ChatGPT, Cursor, VS Code, and other AI tools using OAuth 2.1 or API tokens.

MCP Servers JavaScript Listed Apache-2.0

Is Atlassian Rovo MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 7.2 / 10

Provenance None

Signed commits 40%

Last push 11d ago

Compare Atlassian Rovo MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Atlassian Rovo MCP Server scores 61.1/100 (Grade C), ranked #602 of 1325 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 7.2/10; 40% of recent commits are signed; last pushed 2026-09-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How Atlassian Rovo MCP Server compares in MCP Servers

#337 Desktop Commander MCP 61.3 +0.2
#338 Replicant MCP 61.3 +0.2
#339 Atlassian Rovo MCP Server 61.1 this agent
#340 Xdebug MCP 61.1 ±0
#341 Map Traveler MCP 61.1 ±0

Bars show each HVTrust score; the tick marks Atlassian Rovo MCP Server’s 61.1.

Where the 61.1 comes from

HVTrust dimensions vs the MCP Servers average

61.1 / 100 · 100.0% confidence

Atlassian Rovo MCP Server MCP Servers average (775 agents)

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

11.0 / 25

0.7 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.6 / 17

2.4 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

16.2 / 20

4.1 above avg 12.1

AdoptionLog-scaled stars · package downloads

7.3 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

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

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 dependencies: Anthropic, Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

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

67.0

Activity sub-score · out of 100

#339

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

Activity & Reach

Stars

1.1k

Forks

133

Last Push

2026-09-15

11 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #601

Analysis

Activity Inputs

67.0 / 100

StarsRepository reach

18.2 / 30

FreshnessLast push recency

23.5 / 25

ActivityRecent commits

15.3 / 25

CommunityFork signal

9.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

7.2 / 10

OpenSSF Scorecard · scanned Sep 19, 2026

Signed Commits

40%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 9

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 8

Security-Policy 10

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 10

Common questions about Atlassian Rovo MCP Server

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 7.2/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?

Maintained. Last push was 11 days ago.

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?

40% 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-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 230 spots (#357 → #587)

2026-09-23

HVTrust Changed

HVTrust up 11.7pts (49.8 → 61.5)

2026-09-22

Newly Listed

First tracked at rank #357

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-18

Rank Moved

Rank dropped 12 spots (#546 → #558)

2026-09-15

Rank Moved

Rank rose 15 spots (#556 → #541)

2026-09-12

Rank Moved

Rank dropped 10 spots (#540 → #550)

2026-09-07

Rank Moved

Rank dropped 38 spots (#506 → #544)

2026-09-06

Rank Moved

Rank rose 14 spots (#520 → #506)

2026-09-05

Rank Moved

Rank dropped 70 spots (#450 → #520)

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