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/tonyweckstrom1987/mcp-server-git-historyWrote 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/tonyweckstrom1987/mcp-server-git-history/git-history)<a href="https://agentmods.dev/mcp/tonyweckstrom1987/mcp-server-git-history/git-history"><img src="https://agentmods.dev/badge/mcp/tonyweckstrom1987/mcp-server-git-history/git-history/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/tonyweckstrom1987/mcp-server-git-history/git-history"><img src="https://agentmods.dev/badge/mcp/tonyweckstrom1987/mcp-server-git-history/git-history.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
git-history 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 20d 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
{
"git-history": {
"command": "npx",
"args": [
"-y",
"mcp-server-git-history"
],
"env": {}
}
}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.
- 20d ago First seen · 10 lines scan A e8417e1102ea
git-history is an MCP server published in the GitHub repository tonyweckstrom1987/mcp-server-git-history (0 stars, last pushed 8d 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-09-27.
Other mcp servers, from other repositories
orca-mcp
External MCP server for controlling Orca (worktrees, sessions, orchestration). Runs locally from the orca-mcp npm package. Needs 5 environment variables to run.
git-mcp-server
Comprehensive Git MCP server enabling native git tools including clone, commit, worktree, & more. Runs locally from the @cyanheads/git-mcp-server npm package. Needs 2 environment variables to run.
rpgmaker-mv-ultimate
RPG Maker MV Ultimate: AI copilot to generate, edit and understand RPG Maker MV projects (MCP). Runs locally from the rpgmaker-mv-mcp npm package. Needs 5 environment variables to run.
velog
A local MCP server for Velog, a Korean blogging platform, that lets coding agents read, search, and view statistics, and can create drafts or private posts by default. It runs from an npm package and needs five environment settings.
velog
An MCP server for Velog, a Korean developer blogging platform, with support for reading and writing blog content and creating diagrams or sequences. Public publishing is optional and requires configuration and access credentials.
helpscout
MCP server "helpscout" as configured in drewburchfield/help-scout-mcp-server. Runs dist/cli.js with node. Needs 3 environment variables to run.