@atlassian-dc-mcp/jira

MCPattested
v0.35.0io.github.b1ffUnknownUpdated 11d agonpmGitHub

MCP server for Atlassian Jira Data Center - search, view, and create issues

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
2kDownloads/wk
99GitHub stars
41Forks
11d agoLast update
Reads these credentials
  • JIRA_API_TOKENAPI keyoptional

    Jira Personal Access Token or API token. Required unless provided through ATLASSIAN_DC_MCP_CONFIG_FILE.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.b1ff
LicenseUnknown
Version0.35.0
Sourcenpm+mcp-registry
npm@atlassian-dc-mcp/jira
GitHubb1ff/atlassian-dc-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 98bcabb
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface14 tools · none privileged
Security scan⚠ Warnings (0)v0.29.0 · 1mo agoHow well does this scan work?
CHANGEtool-addedTool surface grew since v0.25.0: added jira_getIssueLinkTypes, jira_linkIssues, jira_unlinkIssues, jira_uploadAttachment, jira_downloadAttachment
EvalsNone
IndexedJun 18, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

14 tools · none privileged
Statically extracted from the published packagev0.29.0 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Surface history
CHANGETool surface grew since v0.25.0: added jira_getIssueLinkTypes, jira_linkIssues, jira_unlinkIssues, jira_uploadAttachment, jira_downloadAttachment
jira_searchIssuesNo description published

This tool published no description. Forge does not invent one.

jira_getIssueNo description published

This tool published no description. Forge does not invent one.

jira_getIssueCommentsNo description published

This tool published no description. Forge does not invent one.

jira_createIssueNo description published

This tool published no description. Forge does not invent one.

jira_updateIssueNo description published

This tool published no description. Forge does not invent one.

jira_postIssueCommentNo description published

This tool published no description. Forge does not invent one.

jira_getTransitionsNo description published

This tool published no description. Forge does not invent one.

jira_getIssueDevelopmentInfoNo description published

This tool published no description. Forge does not invent one.

jira_transitionIssueNo description published

This tool published no description. Forge does not invent one.

jira_getIssueLinkTypesNo description published

This tool published no description. Forge does not invent one.

jira_linkIssuesNo description published

This tool published no description. Forge does not invent one.

jira_unlinkIssuesNo description published

This tool published no description. Forge does not invent one.

jira_uploadAttachmentNo description published

This tool published no description. Forge does not invent one.

jira_downloadAttachmentNo description published

This tool published no description. Forge does not invent one.

0 of 14 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for Atlassian Jira Data Center - search, view, and create issues

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

14 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in project management