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/chmouel/jayrah/jayrahgit clone --depth 1 https://github.com/chmouel/jayrahGrade A, and why
jayrah 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 2d 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
{ "jayrah": { "command": "uvx", "args": [ "jayrah" ] } }
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.
- 2d ago First seen · 8 lines scan A f921a161cf76
jayrah is an MCP server published in the GitHub repository chmouel/jayrah (3 stars, last pushed 6mo ago), licensed Apache-2.0. 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
mcp-jira-stdio
MCP server for Jira Cloud — issues, search, comments, attachments, transitions. Runs locally from the mcp-jira-stdio npm package. Needs 5 environment variables to run.
jira
Model Context Protocol (MCP) server for Jira API integration. Runs locally from the mcp-jira-stdio npm package.
jira
MCP server "jira", hosted remotely at gateway.pipeworx.io, as configured in pipeworx-io/mcp-jira.
zephyr-scale-mcp
Zephyr Scale on self-hosted Jira Server/DC: test cases, cycles, executions, plans and attachments. Runs locally from the zephyr-scale-mcp npm package. Needs 12 environment variables to run.
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.