Vantio Gate runs on your own machine — the client starts it, so there is no endpoint to ping. 32 installs a week from npm. Last commit 13 Sep 2026.
Vantio Gate — Policy Latch dry-run evaluate for agents. No live enforce from MCP.
We read the source, 21 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
path = os.path.join(runs, f"{safe}.json")
const child = spawn(program, programArgs, { stdio: "inherit", env: childEnv, shell: false });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
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": {
"args": [
"-y",
"@vantio/gate-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.vantio-gate]
command = "npx"
args = ["-y", "@vantio/gate-mcp"]
{
"mcpServers": {
"vantio-gate": {
"args": [
"-y",
"@vantio/gate-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"vantio-gate": {
"args": [
"-y",
"@vantio/gate-mcp"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
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)).
The author declared them in the registry entry; get the values from the project itself.
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.
AuthzX MCP Gateway — policy-enforcing proxy between AI agents and MCP servers
Model proof-of-work policy and latency for AI agents. $1 USDC rehearsal; no runtime protection.
Live coding-bounty deal-flow from verified-escrow GitHub bounties for AI agents.
Answers built from our own checks of this server.