MCP, MCP server
Jira Alerts Mcp
Jira Alerts Mcp, an MCP server listed in the PlugVet directory.
Compatibility: Not stated.
Grade B
Minor issues only, no Medium or High. Worth a quick look at the findings below before installing.
Not a guarantee. A hygiene check of the source at the commit shown, not a security audit.
NETWORK_NO_FIXED_HOST SECRETS_PATH_DOTENV OBFUSCATION_FILE_OVER_READ_CAP
Why this grade
- NETWORK_NO_FIXED_HOST Low
Makes a network call whose host is not written as a fixed address.
scripts/refresh-spec.mjs, line 5
* Kept as a script rather than a curl in the README so the hash in - SECRETS_PATH_DOTENV Low
Mentions a .env file.
.env.example, line 8
# set -a; source .env; set +a - OBFUSCATION_FILE_OVER_READ_CAP Note
A file was over the read cap and was not fully read.
spec/jsm-ops.v3.json, line 1
{"openapi":"3.0.1","info":{"contact":{"email":"[email protected]"},"description":"Operations APIs for Jira Service Management","title":"JSM Operations API","version":"1"},"server
Any High, or two or more Medium findings, give D. One Medium gives C. Low findings or a security Note give B. Each code names a finding behind the letter.
Grades are a hygiene check of the source at the commit shown, on the date checked, not a security audit or a guarantee. The free directory grades are automated. Before release, a PlugVet engineer reviews every paid report and any grade we hold back, including all F grades, against the source code and the evidence we quote.
What was checked
Plain notes from the hygiene checks.
Permissions
Pass
No shell or command execution found, and no extra permission was declared.
Install and update
Pass
No install-time script found, and dependencies are pinned or absent.
Network
Concern
can reach a host that is not written as a fixed address.
NETWORK_NO_FIXED_HOST
scripts/refresh-spec.mjs, line 5
* Kept as a script rather than a curl in the README so the hash in
scripts/refresh-spec.mjs, line 19
const response = await fetch(SOURCE, { redirect: "follow" });
Secrets
Concern
reads a credential or environment file.
SECRETS_PATH_DOTENV
.env.example, line 8
# set -a; source .env; set +a
.env.example, line 11
# Copy to `.env` and fill in. `.env` is gitignored - never commit real values.
.gitignore, line 8
# Environment / credentials - never commit a real Atlassian API token
Show more
.gitignore, line 9
.env
.gitignore, line 11
!.env.example
README.md, line 215
[`.env.example`](.env.example) lists these for reference. The server does **not**
README.md, line 216
read `.env` itself - an MCP server is launched by its client, and the client owns
README.md, line 218
`set -a; source .env; set +a` for local development.
Agent instructions
Pass
No instruction to ignore earlier instructions or to hide a step.
Obfuscation
Note
a file was over the read cap and was not fully read.
OBFUSCATION_FILE_OVER_READ_CAP
spec/jsm-ops.v3.json, line 1
{"openapi":"3.0.1","info":{"contact":{"email":"[email protected]"},"description":"Operations APIs for Jira Service Management","title":"JSM Operations API","version":"1"},"server
Licence
Pass
A licence file is present (LICENSE).
Maintainer activity
Pass
The latest commit is within the last 365 days.
Note
Hygiene check of commit 21db08e3fcd8. can reach a host that is not written as a fixed address. reads a credential or environment file. a file was over the read cap and was not fully read.
Date and source
Date checked:
github.com
Commit graded: 21db08e3fcd8aaa1fcfe03d218737654a3ef9293
This link goes to the original host. PlugVet does not host or check what you download from there, and installing it is your own decision and risk.