Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.vish288/mcp-atlassian-extended

PYPI · MCP-ATLASSIAN-EXTENDED · SCANNED SEP 20

MCP server for Jira and Confluence — sprints, agile boards, attachments, versions, calendars.

Available components

pypi · mcp-atlassian-extended 39
0 this week 39 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 2 of 26 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
  • Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
  • Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Tool Safety0
  • Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
  • Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the io.github.vish288/mcp-atlassian-extended server?

io.github.vish288/mcp-atlassian-extended runs locally as a PyPI package, launched with uvx mcp-atlassian-extended. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-atlassian-extended

# add to Claude Code
claude mcp add vish288-mcp-atlassian-extended -- uvx mcp-atlassian-extended
// .cursor/mcp.json
{
  "mcpServers": {
    "vish288-mcp-atlassian-extended": {
      "command": "uvx",
      "args": [
        "mcp-atlassian-extended"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "vish288-mcp-atlassian-extended": {
      "command": "uvx",
      "args": [
        "mcp-atlassian-extended"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add vish288-mcp-atlassian-extended -- uvx mcp-atlassian-extended
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vish288-mcp-atlassian-extended": {
      "type": "local",
      "command": [
        "uvx",
        "mcp-atlassian-extended"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add vish288-mcp-atlassian-extended --command uvx --arg mcp-atlassian-extended
# ~/.hermes/config.yaml
mcp_servers:
  vish288-mcp-atlassian-extended:
    command: "uvx"
    args: ["mcp-atlassian-extended"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "vish288-mcp-atlassian-extended": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-atlassian-extended"
      ]
    }
  }
}
# add to Vellum
assistant mcp add vish288-mcp-atlassian-extended -t stdio -c uvx -a mcp-atlassian-extended
// mcp.json
{
  "mcpServers": {
    "vish288-mcp-atlassian-extended": {
      "command": "uvx",
      "args": [
        "mcp-atlassian-extended"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 0
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.6.16 → 0.8.0 functional
    • Package version: 0.6.16 → 0.7.2 functional
    • Package version: 0.6.16 → 0.7.0 functional
  • 15 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified ▼ security
  • 5 Sept 26 −46
    • Tool safety: pass → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Stability: pass → 0.77 functional
  • 4 Sept 26 0
    • Stability: 0.97 → pass security
  • 3 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed pypi/mcp-atlassian-extended@0.8.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 26 packages
Packages resolved 26
Stale 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the io.github.vish288/mcp-atlassian-extended server?

io.github.vish288/mcp-atlassian-extended is listed in the public MCP registry as io.github.vish288/mcp-atlassian-extended. MCP server for Jira and Confluence, sprints, agile boards, attachments, versions, calendars. This page covers its PyPI package (mcp-atlassian-extended).

Is the io.github.vish288/mcp-atlassian-extended server safe to use?

io.github.vish288/mcp-atlassian-extended scores 39 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the io.github.vish288/mcp-atlassian-extended server still maintained?

io.github.vish288/mcp-atlassian-extended is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.vish288/mcp-atlassian-extended server under?

io.github.vish288/mcp-atlassian-extended declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.