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/garbvalley/jira-github-mcp-mashukWrote 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/garbvalley/jira-github-mcp-mashuk/jira-github-mcp)<a href="https://agentmods.dev/mcp/garbvalley/jira-github-mcp-mashuk/jira-github-mcp"><img src="https://agentmods.dev/badge/mcp/garbvalley/jira-github-mcp-mashuk/jira-github-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
jira-github-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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- jira-github-mcp — 100% identical, 0 lines differ
What it actually says
{ "jira-github-mcp": { "command": "uvx", "args": [ "jira-github-mcp" ] } }
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.
- 7d ago First seen · 8 lines scan A ff69a86d0ca1
jira-github-mcp is an MCP server published in the GitHub repository garbvalley/jira-github-mcp-mashuk (0 stars, last pushed 2mo 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-31.
Other mcp servers, from other repositories
github-projects
GitHub's hosted MCP server: lets the agent search code, read and create issues and pull requests. Remote server at api.githubcopilot.com.
atlassian-mcp
MCP server for self-hosted Jira and Bitbucket (Go, distributed as a prebuilt binary). Runs locally from the @stubbedev/atlassian-mcp npm package.
github
Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github 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.
keelen
Autonomous dev team steered from chat: plain-English requests in, tested merged PRs out. Remote server at keelen.ai.
gitlab
GitLab MCP — wraps the GitLab REST API v4 (BYO API key). Remote server at gateway.pipeworx.io.