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/freema/mcp-jira-stdioWrote 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/freema/mcp-jira-stdio/jira-jira)<a href="https://agentmods.dev/mcp/freema/mcp-jira-stdio/jira-jira"><img src="https://agentmods.dev/badge/mcp/freema/mcp-jira-stdio/jira-jira/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/freema/mcp-jira-stdio/jira-jira"><img src="https://agentmods.dev/badge/mcp/freema/mcp-jira-stdio/jira-jira.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
jira 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 11d 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": {
"command": "npx",
"args": [
"-y",
"mcp-jira-stdio@latest"
]
}
}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.
- 11d ago First seen · 9 lines scan A 3b7e8695769b
jira is an MCP server published in the GitHub repository freema/mcp-jira-stdio (14 stars, last pushed 7d ago), licensed MIT. 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-30.
Other mcp servers, from other repositories
jira
MCP server "jira", hosted remotely at gateway.pipeworx.io, as configured in pipeworx-io/mcp-jira.
atlassian-mcp
MCP server for Atlassian Confluence and Jira Cloud APIs. Runs locally from the @xuandev/atlassian-mcp npm package.
jira-mcp
Jira MCP for controlling Jira through Jira Command Line. Runs locally from the jira-tools-mcp Python package. Needs 2 environment variables to run.
jayrah
A command-line tool for managing Jira issues with FZF. Runs locally from the jayrah Python package.
jira-mcp-server
Model Context Protocol (MCP) server for Jira integration with Claude Code and AI assistants. Provides tools to interact with Jira API: create and manage issues, sprints, boards, projects and workflows. Runs locally from the @carmeloricarte/jira-mcp-server npm package.
cursor-eod-mcp
MCP server for automatically summarizing daily work in Cursor AI and posting EOD status updates to Slack. Runs locally from the @techhalo/cursor-eod-mcp npm package.