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/agentkitai/agentgateWrote 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/agentkitai/agentgate/mcp-agentgate)<a href="https://agentmods.dev/mcp/agentkitai/agentgate/mcp-agentgate"><img src="https://agentmods.dev/badge/mcp/agentkitai/agentgate/mcp-agentgate/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/agentkitai/agentgate/mcp-agentgate"><img src="https://agentmods.dev/badge/mcp/agentkitai/agentgate/mcp-agentgate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentgate 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
{
"agentgate": {
"command": "npx",
"args": [
"-y",
"@agentkitai/agentgate-mcp"
],
"env": {}
}
}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 · 10 lines scan A 52a108cf187c
agentgate is an MCP server published in the GitHub repository agentkitai/agentgate (33 stars, last pushed 5d 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-30.
Other mcp servers, from other repositories
impri
Impri MCP server — human-in-the-loop approval inbox for AI agents. Runs locally from the @impri/mcp npm package. Needs 2 environment variables to run.
agentlens
Tamper-evident, SHA-256 hash-chained audit trail and observability for AI agents. Runs locally from the @agentkitai/agentlens-mcp npm package.
signet-gateway
MCP server "signet-gateway" as configured in bee-san/Signet. Runs locally from the signet-gateway Python package.
gatehouse
Permission tiers, approval gates, and audit logging for MCP servers — the server is the gatekeeper. Runs locally from the mcp-gatehouse Python package.
vitna-compliance-preflight
Pre-action compliance for AI agents: allow, block or hold. 24 statutes, 13 jurisdictions. Runs locally from the @costrinity/vitna-compliance-mcp npm package. Needs 4 environment variables to run.
agentcloud
MCP server "agentcloud", hosted remotely at {agentcloudhost}, as configured in premhiru/agentcloud.