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.
npx agentmods add mcp/green-api/green-api-mcp-gateway/whatsappgit clone --depth 1 https://github.com/green-api/green-api-mcp-gatewayWrote 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/green-api/green-api-mcp-gateway/whatsapp)<a href="https://agentmods.dev/mcp/green-api/green-api-mcp-gateway/whatsapp"><img src="https://agentmods.dev/badge/mcp/green-api/green-api-mcp-gateway/whatsapp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
whatsapp 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 5d 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
{
"whatsapp": {
"url": "https://mcp.green-api.com/mcp",
"type": "streamable-http"
}
}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.
- 5d ago First seen · 6 lines scan A c763d68d2667
whatsapp is an MCP server published in the GitHub repository green-api/green-api-mcp-gateway (0 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
mcp-search
MCP server "mcp-search" as configured in thedotmack/claude-mem. Runs const f=require('fs'),p=require('path'),o=require('os'),c=require('child_process');const h=o.homedir();const C=process.env.CLAUDE_CONFIG_DIR||p.join(h,'.claude');const E=process.env.CLAUDE_PLUGIN_ROOT||process.env.PLUGIN_ROOT||'';const…
claude-flow
Ruflo CLI - Enterprise AI agent orchestration with 60+ specialized agents, swarm coordination, MCP server, self-learning hooks, and vector memory for Claude Code. Runs locally from the @claude-flow/cli npm package. Needs 6 environment variables to run.
stagehand
MCP server "stagehand" as configured in browserbase/stagehand. Runs ../core/dist/facade/stdio-server.mjs with node.
mcp-toolbox
MCP server "mcp-toolbox" as configured in googleapis/mcp-toolbox. Runs in Docker (us-central1-docker.pkg.dev/database-toolbox/toolbox/toolbox:1.9.0).
playwright
MCP server "playwright" as configured in payloadcms/payload. Launched with pnpm dlx @playwright/mcp@latest --caps=vision,verify,tracing,devtools --isolated.
payload
MCP server "payload", hosted remotely at localhost, as configured in payloadcms/payload.