sooperset/mcp-atlassian
MCP server for Atlassian tools (Confluence, Jira)
6k stars · 1.4k forks · Python
Healthy
Healthy: actively maintained by 32 people, no known risks.
Why
No rule fired.
What would change this
- A dormant maintenance status, a deprecated or archived package, a successor link, or a critical advisory would change this.
Maintenance
CompleteActive
- Human commits, 30 days
- 2
- Human commits, 90 days
- 46
- Human commits, 365 days
- 367
- Bot share of commits, 365 days
- 8%
- Last commit
- Sep 19, 2026 (25 days ago)
- Last human commit
- Sep 19, 2026 (25 days ago)
- Authors, 90 days
- 32
- Last release
- Aug 19, 2026 (1 month ago)
- Median PR merge time
- under an hour
Responsiveness: of 29 recent issues, 28% got a maintainer reply. Median first response: 2 days.
Sources: Commits, Releases, Merged pull requests, Issues
People
Complete- Owner
- Personal account
- Commits sampled
- 367 since Oct 14, 2025
- Authors for half of commits
- 1
- Authors for 80% of commits
- 64
- Contributors
- 182
Top committers
- sooperset: 50% of commits
- Troubladore: 4% of commits
- hteichmann-strato: 1% of commits
- cblacknygc: 1% of commits
- major: 1% of commits
Sources: Commits, Contributors
Stars
CompleteOrganic, confidence high
Anyone can buy stars for any repo; bursts alone don't prove the owner did.
- The star history looks organic.
Sources: How star history is analyzed
Risk
CompleteFlags
No risk flags.
License
- Now
- MIT (OSI-approved)
- A year ago
- MIT (OSI-approved)
Packages
No published packages found.
Sources: GitHub: sooperset/mcp-atlassian
Badge
Add this to a README to show the current verdict:
[](https://reporadar.ai/sooperset/mcp-atlassian)Earlier verdicts
- Oct 14, 2026: Healthy
- Oct 14, 2026: Healthy
Computed 7 hours ago · method 2026.10.2