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/LuiccianDev/mcp_git_commit_generatorWrote 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/luicciandev/mcp_git_commit_generator/mcp-git-commit-generator)<a href="https://agentmods.dev/mcp/luicciandev/mcp_git_commit_generator/mcp-git-commit-generator"><img src="https://agentmods.dev/badge/mcp/luicciandev/mcp_git_commit_generator/mcp-git-commit-generator/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/luicciandev/mcp_git_commit_generator/mcp-git-commit-generator"><img src="https://agentmods.dev/badge/mcp/luicciandev/mcp_git_commit_generator/mcp-git-commit-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-git-commit-generator 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
{ "mcp-git-commit-generator": { "command": "uvx", "args": [ "mcp-git-commit-generator" ] } }
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 9d128a7c543f
mcp-git-commit-generator is an MCP server published in the GitHub repository LuiccianDev/mcp_git_commit_generator (0 stars, last pushed 7mo 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
mcp-git-commit-generator
MCP server "mcp-git-commit-generator" as configured in theoklitosBam7/mcp-git-commit-generator. Runs in Docker (ghcr.io/theoklitosbam7/mcp-git-commit-generator:latest).
stdio-mcp-git-commit-generator
MCP server "stdio-mcp-git-commit-generator" as configured in theoklitosBam7/mcp-git-commit-generator. Launched with ${command:python.interpreterPath} -m mcp_git_commit_generator --transport stdio.
http-mcp-git-commit-generator
MCP server "http-mcp-git-commit-generator", hosted remotely at 127.0.0.1, as configured in theoklitosBam7/mcp-git-commit-generator.
uvx-mcp-git-commit-generator
Generate conventional commit messages from your staged git changes using Model Context Protocol (MCP). Runs locally from the mcp-git-commit-generator Python package.
git-helper-ai-mcp
MCP server for git helper ai. Features parse diff, generate commit message, analyze branch. From MEOK AI Labs. Runs locally from the git-helper-ai-mcp Python package.
gitee-mcp-server
MCP Server for using the Gitee API. Runs locally from the gitee-mcp-server npm package.