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/rtahabas/gatewards-sdk/mcp-server-gatewardsgit clone --depth 1 https://github.com/rtahabas/gatewards-sdkWrote 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/rtahabas/gatewards-sdk/mcp-server-gatewards)<a href="https://agentmods.dev/mcp/rtahabas/gatewards-sdk/mcp-server-gatewards"><img src="https://agentmods.dev/badge/mcp/rtahabas/gatewards-sdk/mcp-server-gatewards.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
gatewards 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 4d 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
{
"gatewards": {
"command": "npx",
"args": [
"-y",
"@gatewards/mcp-server"
],
"env": {
"GATEWARDS_API_KEY": "",
"GATEWARDS_GATEWAY_URL": ""
}
}
}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.
- 4d ago First seen · 13 lines scan A 788a067c31d2
gatewards is an MCP server published in the GitHub repository rtahabas/gatewards-sdk (0 stars, last pushed 2mo 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
quesen
Deterministic risk-decision engine and Agent Settlement Protocol for autonomous agents. Remote server at web-production-30ab5.up.railway.app.
agent-context-token-optimizer
MCP server "agent-context-token-optimizer" as configured in DeathOVOGod/agent-context-token-optimizer. Runs locally from the agent-context-token-optimizer Python package.
snaprender
Screenshot, extract content, and render web pages. PNG/JPEG/WebP/PDF, batch, signed URLs. Runs locally from the snaprender-mcp npm package. Needs 1 environment variable to run.
agentfetch
MCP server "agentfetch" as configured in SID1ART/agentfetch. Runs locally from the agentfetch Python package.
network-ai
AI agent orchestration framework for TypeScript/Node.js - 32 adapters (LangChain, AutoGen, CrewAI, OpenAI Assistants, OpenAI Responses, LlamaIndex, Semantic Kernel, Haystack, DSPy, Agno, MCP, OpenClaw, A2A, Codex, MiniMax, NemoClaw, APS, Copilot, LangGrap. Runs locally from the network-ai npm package.
sidclaw-governance-mcp
Governance proxy for MCP servers — policy evaluation, human approval, audit trails. Runs locally from the @sidclaw/sdk npm package. Needs 5 environment variables to run.