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/plugins/freema/mcp-jira-stdio/jira)<a href="https://agentmods.dev/plugins/freema/mcp-jira-stdio/jira"><img src="https://agentmods.dev/badge/plugins/freema/mcp-jira-stdio/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/plugins/freema/mcp-jira-stdio/jira"><img src="https://agentmods.dev/badge/plugins/freema/mcp-jira-stdio/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 1mo 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
{
"name": "jira",
"description": "Jira integration for issue tracking, project management, and workflow automation. Create, update, and search issues directly from Claude.",
"version": "1.0.0",
"author": {
"name": "Tomáš Grasl",
"url": "https://www.tomasgrasl.cz/"
},
"repository": "https://github.com/freema/mcp-jira-stdio",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill, 3 commands, 1 agent, 1 MCP server travel with it, and installing the plugin installs all of them — 83 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 12 lines scan A 738e08a0178f
jira is a plugin published in the GitHub repository freema/mcp-jira-stdio (14 stars, last pushed 18d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
monday.com
Connect your AI agents to monday.com — your work OS for managing projects, tasks, and everyday work.
rosetta-light
Rosetta for Claude - Software Engineering Accelerator instruction set, workflows, and guardrails. (lightweight: simpler workflows, smaller models).
pipefy
Pipefy MCP for Claude Code. Sign in through the browser to manage pipes, cards, tables, reports, automations, and AI agents, and use the included skills to build and analyze processes.
servicenow
ServiceNow MCP server for Claude Code, GitHub Copilot, Codex and any MCP client: Table API, CMDB, schema, aggregates and update sets, plus four Agent Skills. Read-only mode, OAuth client credentials for headless use, audit log.
papi
Persistent project management inside your AI coding tool. PAPI plans what to build next, tracks every decision, and keeps projects coherent across sessions — so a new session starts where the last one left off instead of from nothing.
dev-day
The complete developer day-loop for Claude Code + Jira: /start-session boots a senior-collaborator session (feedback memory, Jira backlog, standing plan-gate), /standup answers 'anything pending?', /bug-triage root-causes tickets, /groom preps them for estimation, /create-ticket files them, /jira-comment posts clean…