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

io.github.raalarcon9705/jira-mcp

NPM · RAALARCON-JIRA-MCP-SERVER · SCANNED AUG 3

Jira & Confluence MCP: 24 tools for issues, sprints, comments, transitions & wiki. Run via npx.

Available components

npm · raalarcon-jira-mcp-server 36
+12 this week 36 Trust /100
Trust breakdown (6 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 →

Supply Chain Security89
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (146 of 148), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (146 of 148), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified

Unverified: 4 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

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · raalarcon-jira-mcp-server

# add to Claude Code
claude mcp add raalarcon9705-jira-mcp -- npx -y raalarcon-jira-mcp-server
# add to Codex CLI
codex mcp add raalarcon9705-jira-mcp -- npx -y raalarcon-jira-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "raalarcon9705-jira-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "raalarcon-jira-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add raalarcon9705-jira-mcp --command npx --arg -y --arg raalarcon-jira-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  raalarcon9705-jira-mcp:
    command: "npx"
    args: ["-y", "raalarcon-jira-mcp-server"]
// mcp.json
{
  "mcpServers": {
    "raalarcon9705-jira-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "raalarcon-jira-mcp-server"
      ]
    }
  }
}
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.

  • 3 Aug 26 −2

    No change was recorded against any check on this day. Supply Chain Security went from 98 to 89.

  • 2 Aug 26 +33
    • Provenance: unverified → fail ▼ security
    • Install scripts: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → partial ▲ security
    • Maintenance: unverified → pass ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • License: unverified → pass ▲ functional
    • Licence: MIT functional
  • 1 Aug 26 0
    • Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
  • 31 Jul 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified ▼ security
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
  • 28 Jul 26 0
    • 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
  • 27 Jul 26 24

    First indexed and scored.

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 146 packages

146 packages in the resolved dependency tree · 136 deprecated · 42 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

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.

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.