Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/rrvrs/jira-alerts-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/rrvrs/jira-alerts-mcp/jira-alerts-mcp)<a href="https://agentmods.dev/mcp/rrvrs/jira-alerts-mcp/jira-alerts-mcp"><img src="https://agentmods.dev/badge/mcp/rrvrs/jira-alerts-mcp/jira-alerts-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/rrvrs/jira-alerts-mcp/jira-alerts-mcp"><img src="https://agentmods.dev/badge/mcp/rrvrs/jira-alerts-mcp/jira-alerts-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
jira-alerts-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"jira-alerts-mcp": {
"command": "npx",
"args": [
"-y",
"jira-alerts-mcp"
],
"env": {
"JSM_CLOUD_ID": "",
"JSM_EMAIL": "",
"JSM_API_TOKEN": "",
"JSM_OAUTH_TOKEN": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 15 lines scan A 0c81afe1a7bf
jira-alerts-mcp is an MCP server published in the GitHub repository rrvrs/jira-alerts-mcp (4 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp-atlassian-extended
Extended MCP tools for Jira and Confluence — attachments, agile boards, sprints, calendars. Runs with writes, or locked read-only via MCPREADONLY. Runs locally from the mcp-atlassian-extended Python package. Needs 9 environment variables to run.
jira-mcp-ai
MCP server for Jira Cloud: JQL search, issue reads and gated writes, comments, worklogs, boards and sprints. API-token auth, plan/apply write safety, read-only by default, no telemetry. Runs locally from the jira-mcp-ai npm package. Needs 43 environment variables to run.
atlassian-mcp-server
MCP server for Atlassian APIs (Jira, Confluence, Bitbucket). Runs locally from the @jagadeesh52423/atlassian-mcp-server npm package.
atlassian-server-mcp
Unified stdio MCP server for Jira, Confluence, and Bitbucket Data Center. Runs locally from the @zaimokuza/atlassian-server-mcp npm package.
jira-mcp
MCP server exposing the Jira REST API (boards, sprints, issues, JQL, and a generic passthrough) for Jira Cloud and Data Center. Runs locally from the @thammarongg/jira-mcp npm package.
mcp-atlassian-attachments
MCP server for downloading Jira and Confluence Cloud attachments and uploading Jira attachments. Runs locally from the mcp-atlassian-attachments Python package. Needs 3 environment variables to run.