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.
npx agentmods add mcp/developmentagentsdd/mcp-jiracloud/opencode-jira-mcpgit clone --depth 1 https://github.com/DevelopmentAgentSDD/MCP-JiraCloudWrote 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/developmentagentsdd/mcp-jiracloud/opencode-jira-mcp)<a href="https://agentmods.dev/mcp/developmentagentsdd/mcp-jiracloud/opencode-jira-mcp"><img src="https://agentmods.dev/badge/mcp/developmentagentsdd/mcp-jiracloud/opencode-jira-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
opencode-jira-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 3d 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
{ "opencode-jira-mcp": { "command": "npx", "args": [ "-y", "@DevelopmentAgentSDD/opencode-jira-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.
- 3d ago First seen · 9 lines scan A 77dac3293493
opencode-jira-mcp is an MCP server published in the GitHub repository DevelopmentAgentSDD/MCP-JiraCloud (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
neverinfamous-memory-journal-mcp
A MCP server built for developers enabling Git based project management with project and personal… Remote server at server.smithery.ai.
agent-claim-mcp
File-claim coordination for parallel AI coding agents: claim files before edits, no stomping. Runs locally from the @vk0/agent-claim-mcp npm package.
smokeball-mcp
MCP server for Smokeball API — full coverage for law firm practice management. Runs locally from the smokeball-mcp Python package.
autonomous-sdlc-command-center
MCP server "autonomous-sdlc-command-center" as configured in Senpai-Sama7/autonomous-sdlc-command-center. Runs locally from the autonomous-sdlc-command-center Python package.
google-tasks-mcp
Manage Google Tasks from MCP-compatible AI clients. Runs locally from the google-tasks-mcp Python package.
australia-tenders
Australia Government Procurement MCP — AusTender OCDS (keyless). Remote server at gateway.pipeworx.io.