Atlassian Dc MCP
MCP servers for the Atlassian products (Bitbucket, Confluence, JIRA) of the Data Center version
Is Atlassian Dc MCP safe? Strong public trust posture, backed by multiple independent signals.
Compare Atlassian Dc MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Atlassian Dc MCP scores 75.5/100 (Grade B), ranked #216 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 3.9/10; 30% of recent commits are signed; last pushed 2026-09-22. Every point is earned from checkable signals — never paid placement. How scoring works →
How Atlassian Dc MCP compares in MCP Servers
- #124 UK Legal Research 75.6 +0.1
- #125 Metro MCP 75.5 ±0
- #126 Atlassian Dc MCP 75.5 this agent
- #127 Code Index MCP 75.5 ±0
- #128 Komodo MCP Server 75.2 −0.3
Bars show each HVTrust score; the tick marks Atlassian Dc MCP’s 75.5.
Where the 75.5 comes from
HVTrust dimensions vs the MCP Servers average
75.5 / 100 · 100.0% confidenceAtlassian Dc MCP MCP Servers average (775 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
62.3 / 100Supply Chain Trust
Common questions about Atlassian Dc MCP
Does Atlassian Dc MCP publish package provenance?
Does Atlassian Dc MCP have an OpenSSF Scorecard?
Is Atlassian Dc MCP actively maintained?
What license does Atlassian Dc MCP use?
Are Atlassian Dc MCP's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/atlassian-dc-mcp)
<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
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