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-github)<a href="https://agentmods.dev/mcp/abhishekkumar2021/mcp-suite/files-github"><img src="https://agentmods.dev/badge/mcp/abhishekkumar2021/mcp-suite/files-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/abhishekkumar2021/mcp-suite/files-github"><img src="https://agentmods.dev/badge/mcp/abhishekkumar2021/mcp-suite/files-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 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
{
"github": {
"command": "npx",
"args": [
"-y",
"@abhishekmcp/github"
],
"env": {
"GITHUB_TOKEN": "",
"GITHUB_CLIENT_ID": "",
"GITHUB_READONLY": ""
}
}
}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 · 14 lines scan A 1bacc4e30a6c
github 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
weeek-mcp
Local MCP server for Weeek (stdio transport) — read-only by default, opt-in write tools. Runs locally from the weeek-mcp npm package. Needs 6 environment variables to run.
gitlab
GitLab MCP — wraps the GitLab REST API v4 (BYO API key). Remote server at gateway.pipeworx.io.
amazing-clickup-mcp
MCP server for the ClickUp public API (v2 + v3, stdio). Runs locally from the amazing-clickup-mcp Python package.
mcp
Manage tasks, sprints, projects, and wiki pages in your Ithura workspace. Runs locally from the ithura-mcp npm package. Needs 3 environment variables to run.
monday-mcp
MCP server "monday-mcp" as configured in ashrocket/monday-mcp. Runs locally from the @ashrocket/monday-mcp npm package.
github-mcp
Public read+write reference MCP server over the GitHub REST API. Env-gated tool groups (read always on, write off by default), fine-grained PAT auth that degrades to the unauthenticated tier, typed rate-limit/error payloads. Reference portfolio implementation, NOT the official GitHub MCP server. Runs locally from the…