Atlassian Dc MCP

MCP servers for the Atlassian products (Bitbucket, Confluence, JIRA) of the Data Center version

MCP Servers TypeScript Grade B Listed MIT
75.8/100
Rank #203 of 1328
Compare Atlassian Dc MCP

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-02 · 6d ago
Recent change
Rank +8

Is Atlassian Dc MCP safe? Atlassian Dc MCP scores 75.8/100 (Grade B), ranked #203 of 1328 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 3.9/10; 29% of recent commits are signed; last pushed 2026-09-02. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-07
Rank Moved
Rank dropped 15 spots (#193 → #208)
2026-09-05
Grade Changed
Trust grade D → B
2026-09-05
Rank Moved
Rank rose 615 spots (#809 → #194)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.9/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
62.4
Activity sub-score · out of 100
#112

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 →

Signals refreshed 2026-09-08 16:17 UTC · Repo last pushed 6 days ago

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
95
Forks
39
Last Push
2026-09-02
6 days ago
Commits (4 wk)
31
Downloads (7d)
4,392
npm
HN mentions (30d)
Open Issues
2
Rank Change
▲5
was #208

Analysis

HVTrust Dimensions vs MCP Servers

75.8 / 100 · 100.0% confidence

Atlassian Dc MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.8 / 25
3.9 above avg 9.9
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.8 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
17.6 / 20
5.4 above avg 12.2
AdoptionLog-scaled stars · package downloads
9.6 / 20
2.7 above avg 6.9

Activity Inputs

62.4 / 100
StarsRepository reach
11.9 / 30
FreshnessLast push recency
24.2 / 25
ActivityRecent commits
18.8 / 25
CommunityFork signal
7.4 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
3.9 / 10
OpenSSF Scorecard · scanned Sep 6, 2026
Signed Commits
29%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 9
CII-Best-Practices 0
Code-Review 6
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 2
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is Atlassian Dc MCP safe?

Public supply-chain signals for Atlassian Dc MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Atlassian Dc MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does Atlassian Dc MCP publish package provenance?
Yes. Atlassian Dc MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Atlassian Dc MCP have an OpenSSF Scorecard?
Atlassian Dc MCP has an OpenSSF Scorecard score of 3.9/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 Dc MCP actively maintained?
Actively maintained. The repository was pushed to within the last 6 day(s).
What license does Atlassian Dc MCP use?
Atlassian Dc MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Atlassian Dc MCP's commits signed?
28% of the last 100 commits to Atlassian Dc MCP 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 Dc MCP 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
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 Atlassian Dc MCP'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: declared → none

Maintain Atlassian Dc MCP?

For maintainers

HVTrust scores Atlassian Dc MCP 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.

Reputation Timeline

Signal history
Rank 18HVTrust 12Grade 11Score 3Listed 1Surface 1Scorecard 1
2026-09-07
Rank Moved
Rank dropped 15 spots (#193 → #208)
2026-09-05
Grade Changed
Trust grade D → B
2026-09-05
Rank Moved
Rank rose 615 spots (#809 → #194)
2026-09-05
HVTrust Changed
HVTrust up 26.3pts (49.1 → 75.4)
2026-09-04
Rank Moved
Rank dropped 33 spots (#776 → #809)
2026-09-03
Rank Moved
Rank dropped 43 spots (#733 → #776)
2026-09-02
Grade Changed
Trust grade B → D
2026-09-02
Rank Moved
Rank dropped 595 spots (#138 → #733)
2026-09-02
HVTrust Changed
HVTrust down 26.0pts (75.2 → 49.2)
2026-08-31
Grade Changed
Trust grade D → B
2026-08-31
Rank Moved
Rank rose 508 spots (#644 → #136)
2026-08-31
HVTrust Changed
HVTrust up 26.3pts (48.7 → 75.0)
2026-08-30
Grade Changed
Trust grade B → D
2026-08-30
Rank Moved
Rank dropped 468 spots (#176 → #644)
2026-08-30
HVTrust Changed
HVTrust down 22.1pts (70.8 → 48.7)
2026-08-30
Activity Score Changed
Activity score up 6pts (56 → 62)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.8/10
2026-08-29
Grade Changed
Trust grade C → B
2026-08-29
Rank Moved
Rank rose 140 spots (#316 → #176)
2026-08-29
HVTrust Changed
HVTrust up 8.0pts (62.8 → 70.8)
2026-08-26
Rank Moved
Rank rose 44 spots (#353 → #309)
2026-08-26
HVTrust Changed
HVTrust up 3.9pts (59.0 → 62.9)
2026-08-26
Activity Score Changed
Activity score up 16pts (40 → 56)
2026-08-25
Rank Moved
Rank dropped 37 spots (#316 → #353)
2026-08-25
Activity Score Changed
Activity score down 6pts (46 → 40)
2026-08-24
Grade Changed
Trust grade D → C
2026-08-24
Rank Moved
Rank rose 329 spots (#645 → #316)
2026-08-24
HVTrust Changed
HVTrust up 21.6pts (39.5 → 61.1)
2026-08-22
Grade Changed
Trust grade C → D
2026-08-22
Rank Moved
Rank dropped 347 spots (#296 → #643)
2026-08-22
HVTrust Changed
HVTrust down 22.6pts (62.2 → 39.6)
2026-08-21
Rank Moved
Rank dropped 25 spots (#271 → #296)
2026-08-19
Grade Changed
Trust grade D → C
2026-08-19
Rank Moved
Rank rose 346 spots (#616 → #270)
2026-08-19
HVTrust Changed
HVTrust up 22.6pts (40.9 → 63.5)
2026-08-17
Grade Changed
Trust grade C → D
2026-08-17
Rank Moved
Rank dropped 357 spots (#260 → #617)
2026-08-17
HVTrust Changed
HVTrust down 23.1pts (64.0 → 40.9)
2026-08-13
Grade Changed
Trust grade D → C
2026-08-13
Rank Moved
Rank rose 334 spots (#593 → #259)
2026-08-13
HVTrust Changed
HVTrust up 22.3pts (41.5 → 63.8)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-12
Grade Changed
Trust grade C → D
2026-08-12
Rank Moved
Rank dropped 357 spots (#236 → #593)
2026-08-12
HVTrust Changed
HVTrust down 23.1pts (64.6 → 41.5)
2026-08-10
Rank Moved
Rank dropped 17 spots (#218 → #235)
2026-08-08
Newly Listed
First tracked at rank #237

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 75.8 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/atlassian-dc-mcp.svg)](https://hvtracker.net/agents/atlassian-dc-mcp)
HTML:
<a href="https://hvtracker.net/agents/atlassian-dc-mcp"><img src="https://hvtracker.net/badge/atlassian-dc-mcp.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