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/Abhishekkumar2021/mcp-suiteWrote 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/abhishekkumar2021/mcp-suite/files-git)<a href="https://agentmods.dev/mcp/abhishekkumar2021/mcp-suite/files-git"><img src="https://agentmods.dev/badge/mcp/abhishekkumar2021/mcp-suite/files-git/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/abhishekkumar2021/mcp-suite/files-git"><img src="https://agentmods.dev/badge/mcp/abhishekkumar2021/mcp-suite/files-git.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
git 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
{
"git": {
"command": "npx",
"args": [
"-y",
"@abhishekmcp/git"
],
"env": {
"GIT_ROOTS": "",
"GIT_WRITABLE": ""
}
}
}What else server.json configures
This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 13 lines scan A e3c46276dfe1
git is an MCP server published in the GitHub repository Abhishekkumar2021/mcp-suite (1 stars, last pushed 3mo 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
leakferret
Context-aware secret scanner: lets an AI agent scan, verify, and rewrite secrets before committing. Runs locally from the @leakferret/mcp npm package.
commit-message-ai-mcp
AI-powered commit message ai MCP server for agents. Supports generate commit, parse diff, suggest type. By MEOK AI Labs. Runs locally from the commit-message-ai-mcp 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.
github-projects
GitHub's hosted MCP server: lets the agent search code, read and create issues and pull requests. Remote server at api.githubcopilot.com.
token-lens
Context window token analysis and budget management. Runs locally from the token-lens-mcp npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.