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/bee-san/SignetWrote 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/bee-san/signet/signet-gateway)<a href="https://agentmods.dev/mcp/bee-san/signet/signet-gateway"><img src="https://agentmods.dev/badge/mcp/bee-san/signet/signet-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/bee-san/signet/signet-gateway"><img src="https://agentmods.dev/badge/mcp/bee-san/signet/signet-gateway.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
signet-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 9d 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
{ "signet-gateway": { "command": "uvx", "args": [ "signet-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.
- 9d ago First seen · 8 lines scan A ec22f144c2bc
signet-gateway is an MCP server published in the GitHub repository bee-san/Signet (1 stars, last pushed yesterday), 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
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.
orangerail
Turns your Prisma schema into typed MCP tools, with destructive writes gated behind human approval. Runs locally from the orangerail npm package. Needs 1 environment variable to run.
plain-example
MCP server "plain-example", hosted remotely at plain-example.plaintunnel.com, as configured in dropseed/plain.
fluxgit-mcp-server
MCP server "fluxgit-mcp-server" as configured in fluxgit-hq/fluxgit-mcp-server. Launched with fluxgit-mcp-sidecar.
obsidian-wiki
MCP server "obsidian-wiki" as configured in MarcusJellinghaus/mcp-tools-py. Launched with cmd /c npx -y obsidian-mcp ${USERPROFILE}\Documents\GitHub\obsidian-dev-wiki.