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/mjdevaccount/AIStack-MCPInstalling this writes the configuration, not the program: `powershell` has to be on your PATH already, or the server will not start.
Wrote 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/mjdevaccount/aistack-mcp/github)<a href="https://agentmods.dev/mcp/mjdevaccount/aistack-mcp/github"><img src="https://agentmods.dev/badge/mcp/mjdevaccount/aistack-mcp/github/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/mjdevaccount/aistack-mcp/github"><img src="https://agentmods.dev/badge/mcp/mjdevaccount/aistack-mcp/github.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
github 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
{
"github": {
"command": "powershell",
"args": [
"-NoProfile",
"-NonInteractive",
"-ExecutionPolicy",
"Bypass",
"-File",
"C:\\AIStack-MCP\\scripts\\run_github_mcp.ps1"
]
}
}What else mcp.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.
- 20d ago First seen · 13 lines scan A d03ea6494a71
github is an MCP server published in the GitHub repository mjdevaccount/AIStack-MCP (2 stars, last pushed 3d 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
io.github.github/github-mcp-server
MCP server "io.github.github/github-mcp-server" as configured in sharfuddin18/Codemaster-Ai. Runs in Docker (ghcr.io/github/github-mcp-server:1.0.3).
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.
mcp-git-historian
MCP server "mcp-git-historian" as configured in AleBrito124356/mcp-git-historian. Runs locally from the mcp-git-historian Python package.
pdf-suite-mcp
37 tools to read, create, merge, split, watermark, fill, redact & search PDFs. Local, no API key. Runs locally from the pdf-suite-mcp npm package.
opengist-mcp
Read, create, update and delete gists on a self-hosted Opengist instance. Runs locally from the opengist-mcp npm package. Needs 6 environment variables to run.
git-history
Give AI agents Git history tools: commit search, file history, blame, contributors, ref diffs. Runs locally from the mcp-server-git-history npm package.