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/RABNEER/AgentBoxWrote 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/rabneer/agentbox/agentbox-mail)<a href="https://agentmods.dev/mcp/rabneer/agentbox/agentbox-mail"><img src="https://agentmods.dev/badge/mcp/rabneer/agentbox/agentbox-mail/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/rabneer/agentbox/agentbox-mail"><img src="https://agentmods.dev/badge/mcp/rabneer/agentbox/agentbox-mail.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentbox-mail 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
{ "agentbox-mail": { "command": "npx", "args": [ "-y", "agentbox-mail" ] } }
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 · 9 lines scan A fa45b78e7153
agentbox-mail is an MCP server published in the GitHub repository RABNEER/AgentBox (3 stars, last pushed 1mo 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
example
MCP server "example", hosted remotely at mcp.example.com, as configured in intellectronica/ruler.
healthclaw-guardrails
Guardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation. Remote server at mcp-server-production-5112.up.railway.app.
universal-connector-mcp
A security-first, local-first MCP server that connects any API (OpenAPI/GraphQL/gRPC/SOAP) to AI agents through a single normalized operation model. Runs locally from the universal-connector-mcp Python package. Needs 5 environment variables to run.
openapi-to-mcp
Turn any OpenAPI 3.x spec into a live Model Context Protocol (MCP) server: every endpoint becomes a validated tool your AI agent can call. Runs locally from the @karlangas12/openapi-to-mcp npm package.
mcp
The official AraraHQ MCP server for operating WhatsApp support, billing and scheduling with OAuth. Runs locally from the @ararahq/mcp npm package.
nodeproxy
Python clients for NodeProxy, TokenSqueezer, and VectorCache x402 agent APIs. Runs locally from the nodeproxy-tools Python package.