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/sairam0424/ag-bashWrote 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/sairam0424/ag-bash/mcp-server-ag-bash)<a href="https://agentmods.dev/mcp/sairam0424/ag-bash/mcp-server-ag-bash"><img src="https://agentmods.dev/badge/mcp/sairam0424/ag-bash/mcp-server-ag-bash/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/sairam0424/ag-bash/mcp-server-ag-bash"><img src="https://agentmods.dev/badge/mcp/sairam0424/ag-bash/mcp-server-ag-bash.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ag-bash 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.
This is a copy
88% identical to ag-bash — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"ag-bash": {
"command": "npx",
"args": [
"-y",
"@ag-bash/mcp-server"
],
"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.
- 1mo ago First seen · 10 lines scan A 654ca37125b5
ag-bash is an MCP server published in the GitHub repository sairam0424/ag-bash (1 stars, last pushed today), licensed Apache-2.0. 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. It is 88% identical to ag-bash, differing in 5 lines, and is treated as a copy.
Other mcp servers, from other repositories
mcp-victoriametrics
MCP server "mcp-victoriametrics" as configured in VictoriaMetrics/mcp-victoriametrics. Runs in Docker (ghcr.io/victoriametrics/mcp-victoriametrics:1.20.2). Needs 7 environment variables to run.
signoz-mcp-server
MCP server "signoz-mcp-server" as configured in SigNoz/signoz-mcp-server. Runs in Docker (docker.io/signoz/signoz-mcp-server:v0.9.0).
mcp-victorialogs
MCP server "mcp-victorialogs" as configured in VictoriaMetrics/mcp-victorialogs. Runs in Docker (ghcr.io/victoriametrics/mcp-victorialogs:1.9.0). Needs 3 environment variables to run.
dynatrace-managed-mcp
MCP server for Dynatrace Managed to access logs, events, and metrics. Runs locally from the @dynatrace-oss/dynatrace-managed-mcp-server npm package. Needs 5 environment variables to run.
dynatrace-managed
Model Context Protocol (MCP) server for Dynatrace Managed (self-hosted). Runs locally from the @dynatrace-oss/dynatrace-managed-mcp-server npm package. Needs 3 environment variables to run.
greptimedb-mcp-server
MCP server for GreptimeDB with SQL/TQL/PromQL support, sensitive data masking, and prompt templates for observability data analysis. Runs locally from the greptimedb-mcp-server Python package. Needs 13 environment variables to run.