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/letya999/jira-daily-pm-radarWrote 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/letya999/jira-daily-pm-radar/jira-daily-pm-radar-mcp)<a href="https://agentmods.dev/mcp/letya999/jira-daily-pm-radar/jira-daily-pm-radar-mcp"><img src="https://agentmods.dev/badge/mcp/letya999/jira-daily-pm-radar/jira-daily-pm-radar-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/letya999/jira-daily-pm-radar/jira-daily-pm-radar-mcp"><img src="https://agentmods.dev/badge/mcp/letya999/jira-daily-pm-radar/jira-daily-pm-radar-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
jira-daily-pm-radar-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 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-daily-pm-radar-mcp": { "command": "npx", "args": [ "-y", "jira-daily-pm-radar-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.
- 11d ago First seen · 9 lines scan A 62d1eb3283cc
jira-daily-pm-radar-mcp is an MCP server published in the GitHub repository letya999/jira-daily-pm-radar (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
cli
A local-first registry of every project on your machine, exposed to your coding agents via MCP. Runs locally from the @itacajs/cli npm package.
agendum
Universal project management for AI coding agents — MCP server + CLI + git-native task board. Runs locally from the agendum Python 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.
a2atlassian
Agent-to-Atlassian — CLI and MCP server for AI agents to work with Jira & Confluence. Runs locally from the a2atlassian Python package.
jayrah
A command-line tool for managing Jira issues with FZF. Runs locally from the jayrah Python package.
crmy
CRMy CLI — Local CLI + stdio MCP server. Runs locally from the @crmy/cli npm package.