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/arshan846/pluto-aguardWrote 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/arshan846/pluto-aguard/github)<a href="https://agentmods.dev/mcp/arshan846/pluto-aguard/github"><img src="https://agentmods.dev/badge/mcp/arshan846/pluto-aguard/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/arshan846/pluto-aguard/github"><img src="https://agentmods.dev/badge/mcp/arshan846/pluto-aguard/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": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GITHUB_PERSONAL_ACCESS_TOKEN",
"ghcr.io/github/github-mcp-server"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_FAKE_TOKEN_FOR_TESTING_ONLY_00000000"
}
}
}What else claude_desktop_config.json configures
This page is one entry in a file that holds 3. 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 · 16 lines scan A 22a09f0c6773
github is an MCP server published in the GitHub repository arshan846/pluto-aguard (4 stars, last pushed 3mo ago), 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. 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
filesystem
Gives the agent read and write access to a set of allowed directories on the local filesystem. Runs locally from the @modelcontextprotocol/server-filesystem npm package.
shell
MCP server "shell" as configured in opena2a-org/hackmyagent. Runs locally from the @anthropic/mcp-shell-server npm package.
sunglasses
MCP server "sunglasses" as configured in sunglasses-dev/sunglasses. Runs sunglasses.mcp with python3.
agent-sec
Zero-install security baseline for AI coding agents — OWASP/CWE-cited rules over MCP. Remote server at agentsec.kernora.ai.
heron
MCP server "heron", hosted remotely at heronapp.io, as configured in heronsec/heron-mcp.
dfx-agentguard
Autonomous security scanner for AI agents. Detects prompt injection, tool abuse, data exfiltration, and OWASP ASI Top 10 vulnerabilities. Runs locally from the dfx-agentguard Python package.