mcp-jira-stdio@1.12.2
VERIFIED· not startedPublisher claims: "Model Context Protocol (MCP) server for Jira API integration" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Not enough was observed to say yet. Not started: dependency install failed; the server itself was not observed. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try mcp-jira-stdio` runs it now and prints the full answer.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-07 and scored it 88/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 1 s · 2 scenarios · 0 deviationsStatic findings
let o = j.resolve(process.cwd(), ".env"), t = "utf8", n = process.env;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log(`- .env email: ${JIRA_EMAIL}`);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log(`\n${colors.green}✅ Created .env file for development${colors.reset}`);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const envPath = path.join(projectPath, '.env');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log('\nYou should update JIRA_EMAIL in your .env file to: ' + json.emailAddress);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- Verify your account has the necessary permissionsFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.// Create .env file optionFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.let o = Ce(), t = { encoding: o.encoding || "utf8", quiet: o.quiet === true, debug: o.debug === true, override: o.override === true, fast: o.fast === true, paths: [".env"], defaultPath: true };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`\n${colors.yellow}Create .env file for development? (y/n): ${colors.reset}`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log(["Usage: dotenv run [--help] [-q|--quiet] [--debug] [--override] [--fast] [-f|--file <paths>] [--] <command> [args...]", "", "Run a command with environment variables from a .env file.", "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for mcp-jira-stdio@1.12.2 as of 7d ago. This is the package itself, not its dependencies.