Skills/PyPI/mcp-server-r4j

mcp-server-r4j@0.1.2

VERIFIED· not started

Publisher claims: "MCP server for R4J (Requirements for Jira) — manage folders, issues, and tree structure in Jira Data Center" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher christian-epple · publishing for 208 daysInstalls 37Last detonated 5d ago
$claude mcp add mcp-server-r4j -- uvx mcp-server-r4j
WatchReport an issue

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

It will ask for
R4J_JIRA_PATConfiguration, not credentials: R4J_CA_BUNDLE, R4J_DEBUG, R4J_JIRA_URL, R4J_PROJECT_KEY, R4J_TIMEOUT_SECONDS, R4J_VERIFY_SSL
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for R4J_JIRA_PAT and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --net declared -- uvx mcp-server-r4j

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-09 and scored it 84/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 · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

MEDIUM
Access to sensitive file pathstests/README.md:37 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files| `R4J_JIRA_URL` | `.env` | real Jira URL |Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Python subprocess execution detectedtests/test_config.py:37 · Python subprocess execution detectedreturn subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
MCP server using network transport (SSE/HTTP)tests/conftest.py:14 · MCP server using network transport (SSE/HTTP) — data sent over network``mcp_server_r4j`` module holds a module-level ``httpx.AsyncClient`` that bindsFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_smoke.py:24 · MCP server using network transport (SSE/HTTP) — data sent over networkis necessary because ``mcp_server_r4j`` holds a module-level ``httpx.AsyncClient``Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
HIGH
Access to sensitive file pathsCLAUDE.md:33 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files…s if env set ``` Unit tests run without credentials. Live smoke tests require `.env` + `R4J_TEST_SANDBOX_PARENT_PATH`; bulk-op and preview smoke tests additionally…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/README.md:28 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filescollection, without overriding real values loaded from `.env`.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/README.md:39 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files| `R4J_PROJECT_KEY` | `.env` | real project key |Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/README.md:40 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files| `R4J_TEST_SANDBOX_PARENT_PATH` | `.env` (test-only) | path of a folder where tests may create/destroy child folders |Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/README.md:38 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files| `R4J_JIRA_PAT` | `.env` | real PAT |Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/conftest.py:7 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesdeliberately chosen so real values from ``.env`` or the shell areFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_smoke.py:5 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- ``R4J_JIRA_URL``, ``R4J_JIRA_PAT``, ``R4J_PROJECT_KEY`` — from ``.env``Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈3,279 tok
2 files · 15 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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-server-r4j@0.1.2 as of 5d ago. This is the package itself, not its dependencies.