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/getagentomy/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/getagentomy/mcp-gateway/agentomy-mcp-gateway)<a href="https://agentmods.dev/mcp/getagentomy/mcp-gateway/agentomy-mcp-gateway"><img src="https://agentmods.dev/badge/mcp/getagentomy/mcp-gateway/agentomy-mcp-gateway/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/getagentomy/mcp-gateway/agentomy-mcp-gateway"><img src="https://agentmods.dev/badge/mcp/getagentomy/mcp-gateway/agentomy-mcp-gateway.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentomy-mcp-gateway 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 8d 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
{ "agentomy-mcp-gateway": { "command": "npx", "args": [ "-y", "agentomy-mcp-gateway" ] } }
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.
- 8d ago First seen · 9 lines scan A 02d36ce889b8
agentomy-mcp-gateway is an MCP server published in the GitHub repository getagentomy/mcp-gateway (0 stars, last pushed 6d 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
mcp-server
Exact-action approval for consequential agent actions: request, track, and verify signed receipts. Runs locally from the @emilia-protocol/mcp-server npm package. Needs 3 environment variables to run.
mcp
Authorize consequential AI agent actions before execution. Runs locally from the @decionis/mcp npm package. Needs 1 environment variable to run.
termlink
MCP server "termlink" as configured in DimitriGeelen/agentic-engineering-framework. Launched with termlink mcp serve. Needs 1 environment variable to run.
fw
MCP server "fw" as configured in DimitriGeelen/agentic-engineering-framework. Runs agents/mcp/framework_mcp_server.py with python3.
arifos
Constitutional AI kernel with 13 MCP tools, 888JUDGE verdict pipeline, and VAULT999 ledger. Remote server at arifos.arif-fazil.com.
arifos-mcp
mcp-name: io.github.ariffazil/arifos | .ariffazil/arifos | arifOS v1!2026.7.26 — Constitutional AI Governance Kernel. 8 kernel ABI capabilities → 6 public tools (arifverbnoun, generated from arifosmcp/abi/capabilityregistry.json), dynamic F1-F13 enforcement via ConstitutionKernel + FloorEvaluator, VAULT999 immutable…