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/tya5/issuehub.cliWrote 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/tya5/issuehub.cli/issuehub-cli)<a href="https://agentmods.dev/mcp/tya5/issuehub.cli/issuehub-cli"><img src="https://agentmods.dev/badge/mcp/tya5/issuehub.cli/issuehub-cli/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/tya5/issuehub.cli/issuehub-cli"><img src="https://agentmods.dev/badge/mcp/tya5/issuehub.cli/issuehub-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
issuehub-cli 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
{ "issuehub-cli": { "command": "uvx", "args": [ "issuehub-cli" ] } }
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 · 8 lines scan A b69bebabbad5
issuehub-cli is an MCP server published in the GitHub repository tya5/issuehub.cli (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
overseer-nvim-mcp
Gives coding agents the user's own view and control of overseer.nvim tasks in Neovim. Runs locally from the overseer-nvim-mcp npm package.
git-org-group-cred-vault
MCP server "git-org-group-cred-vault" as configured in wildfirebill-ai/git-org-group-cred-vault. Runs locally from the git-org-group-cred-vault npm package.
iwe
Markdown knowledge base as agent memory. Runs against the notes directory it is started in. Runs locally from the @iwe-org/mcp npm package.
obsidian-github-mcp
MCP server "obsidian-github-mcp" as configured in SarutobiSasuke8/obsidian-github-mcp. Runs locally from the @sarutobi-sasuke/obsidian-github-mcp npm package.
gitlab
GitLab MCP — wraps the GitLab REST API v4 (BYO API key). Remote server at gateway.pipeworx.io.
gitlab-mcp
MCP server (stdio) — proxy fino sobre a REST API v4 de um GitLab CE self-hosted, focado em navegar MRs e deixar review inline. Runs locally from the @vinihcrosa/gitlab-mcp npm package.