Vantio Gate runs on your own machine — the client starts it, so there is no endpoint to ping. 46 installs a week from npm. Last commit 6 Nov 2026.
Vantio Gate — Policy Latch dry-run evaluate for agents. No live enforce from MCP.
We read the source, 2 d ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
const absolute = path.join(root, relative);
const result = spawnSync(process.execPath, ["-e", script], {
completed = subprocess.run(
_SKIP_NAMES = ("id_rsa", "id_dsa", "credentials", "secret.token")
if "--privileged" in argv or "--cgroup-parent" in argv:
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Today is the operative word: we check Vantio Gate every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add vantio-gate -- npx -y @vantio/gate-mcp
{
"mcpServers": {
"vantio-gate": {
"command": "npx",
"args": [
"-y",
"@vantio/gate-mcp"
]
}
}
}
[mcp_servers.vantio-gate]
command = "npx"
args = ["-y", "@vantio/gate-mcp"]
{
"mcpServers": {
"vantio-gate": {
"command": "npx",
"args": [
"-y",
"@vantio/gate-mcp"
]
}
}
}
{
"servers": {
"vantio-gate": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@vantio/gate-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
VANTIO_API_KEY (Optional Pro API key for gate_get_policy / gate_residual_risk against your control plane), VANTIO_API_BASE (Optional Pro API base URL (default https://api.vantio.ai)).
AI agent governance for MCP: PII detection, policy enforcement, compliance, and kill switch.
Read-only evidence for the tools agents run: MCP server records, coverage and policy.
MCP policy proxy: spend caps, approvals for destructive tools, kill switch, dry-run, audit log.
Deterministic policy enforcement and MCP management for AI agent tool calls.
Episodic memory, Frames, Policy Neighborhoods, and policy enforcement for AI agents.
Model proof-of-work policy and latency for AI agents. $1 USDC rehearsal; no runtime protection.
AuthzX MCP Gateway — policy-enforcing proxy between AI agents and MCP servers
Premium agentic endpoint for api-rate-limit-enforcer-mcp.
Answers built from our own checks of this server.