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/nickgeorgeseo/mcp-gatehouseWrote 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/nickgeorgeseo/mcp-gatehouse/gatehouse)<a href="https://agentmods.dev/mcp/nickgeorgeseo/mcp-gatehouse/gatehouse"><img src="https://agentmods.dev/badge/mcp/nickgeorgeseo/mcp-gatehouse/gatehouse/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/nickgeorgeseo/mcp-gatehouse/gatehouse"><img src="https://agentmods.dev/badge/mcp/nickgeorgeseo/mcp-gatehouse/gatehouse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gatehouse 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
{
"gatehouse": {
"command": "uvx",
"args": [
"mcp-gatehouse"
],
"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 · 9 lines scan A 42893e4bf08f
gatehouse is an MCP server published in the GitHub repository nickgeorgeseo/mcp-gatehouse (2 stars, last pushed 3d 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
sysknife
MCP server "sysknife" as configured in lacs-project/sysknife. Launched with sysknife-cli. Needs 1 environment variable to run.
agentgate
Human-in-the-loop approval gateway for AI agents over MCP: request, decide, approve. Runs locally from the @agentkitai/agentgate-mcp npm package.
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.
midplane
Safe-by-default SQL guardrails for AI agents: AST-checked queries, per-table policy, audit log. Runs locally from the midplane npm package. Needs 4 environment variables to run.
mcp-audit-proxy
Transparent audit proxy for MCP servers: logs every tool call, flags poisoning and rug pulls. Runs locally from the mcp-audit-proxy npm package.
kernel
Open proof-required execution kernel for consequential actions. Runs locally from the actenon-kernel Python package.