Vengtoo MCP Gateway logo

Vengtoo MCP Gateway

Policy-enforcing proxy that authorizes and audits MCP tool calls between agents and downstream MCP servers.

Install Vengtoo MCP Gateway

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-gateway-2": {
      "command": "npx",
      "args": [
        "-y",
        "vengtoo-mcp-gateway"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command didn't complete successfully in our automated test.

npx -y vengtoo-mcp-gateway

npm notice npm notice New major version of npm available! 10.1.0 -> 12.2.0 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v12.2.0> npm notice Run `npm install -g npm@12.2.0` to update! npm notice npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/vengtoo-mcp-gateway - Not found npm ERR! 404 npm ERR! 404 'vengtoo-mcp-gateway@*' is not in this registry. npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, http ur

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked .

Overview

Vengtoo MCP Gateway MCP server places an authorization layer between MCP clients and downstream MCP servers. It intercepts tool calls, evaluates them through either Vengtoo Cloud or a local Vengtoo Agent, and forwards only allowed requests. The gateway supports local stdio for desktop agents and Streamable HTTP for remote or shared deployments. Reach for it when MCP tools need centralized policy checks, caller identity, or structured invocation logs.

Use cases

  • Authorize database and filesystem MCP tool calls before execution
  • Enforce Rego policies for local offline agent deployments
  • Route multiple MCP servers through one governed gateway
  • Attribute shared HTTP gateway calls to individual agents
  • Audit allowed and denied MCP tool invocations

Key features

  • Per-call authorization checks
  • Local Vengtoo Agent and Rego policy mode
  • Vengtoo Cloud policy mode
  • Structured tool-call audit logging
  • stdio and Streamable HTTP transports
  • HTTP caller token-to-subject mapping

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

21/25 checks healthy over the last 95d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · vengtoo-mcp-gateway (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit3mo agoMost recent push to the default branch.
Install checkInconclusiveInstall command did not finish in our automated test.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Vengtoo MCP Gateway works

What Vengtoo MCP Gateway MCP server does

Vengtoo MCP Gateway MCP server proxies MCP tools from one or more downstream servers to an MCP client. Before forwarding a tool invocation, it sends an authorization request to either a local Vengtoo Agent or the Vengtoo Cloud API. The decision determines whether the call proceeds.

The gateway does not provide a fixed catalog of business tools. Instead, it exposes the tools offered by the configured downstream MCP servers and applies policy to their calls. A configuration identifies each server by a command, optional arguments, and optional environment variables.

Every invocation produces a structured audit record containing details such as the subject, tool name, arguments, authorization decision, and latency. This makes the gateway suitable for environments where tool usage must be reviewed or attributed to an agent identity.

How it works

In local mode, run the Vengtoo Agent with a Rego policy file and configure the gateway with the agent URL. Policies can allow specific tools and inspect arguments, including blocking SQL patterns such as destructive statements. Local mode is designed to operate without a cloud account.

Cloud mode sends authorization checks to a Vengtoo Cloud endpoint and uses an API key. The gateway configuration supplies the agent subject, subject type, and resource type used in policy evaluation. A default subject type of agent and resource type of mcp_tool are available when these fields are omitted.

The default stdio transport runs the gateway as a local subprocess over standard input and output. HTTP transport exposes a Streamable HTTP MCP endpoint for remote callers or multiple concurrent agents. HTTP callers can use separate bearer tokens mapped to separate subjects, allowing policies and audit records to distinguish agents. Sessions remain associated with the token that created them.

Setup and configuration

Vengtoo MCP Gateway MCP server requires Node.js 18 or newer. Install the package with the repository's published npm package, then create a JSON configuration containing either vengtoo.agentUrl or vengtoo.cloudUrl, a subject, and at least one entry under servers.

For local authorization, install and start the Vengtoo Agent with a .rego policy file. For cloud authorization, provide the cloud URL and API key; the key may be placed in the configuration or supplied through VENGTOO_API_KEY.

Use the stdio transport for a desktop client such as Claude Desktop, Cursor, or Claude Code. Set transport to http, or pass --http, to enable the HTTP endpoint. HTTP settings include the bind host, port, MCP path, caller tokens, anonymous access tokens, and host or origin allowlists.

When HTTP binds to a non-loopback interface, caller authentication is required unless VENGTOO_GATEWAY_ALLOW_UNAUTHENTICATED=true is explicitly set. The /healthz endpoint remains available without authentication.

Tools and capabilities

  • Proxies tools from configured downstream MCP servers.
  • Checks authorization before each tool call.
  • Supports local Rego-based decisions through Vengtoo Agent.
  • Supports managed policy evaluation through Vengtoo Cloud.
  • Records structured audit events for tool invocations.
  • Provides stdio and Streamable HTTP MCP transports.
  • Maps HTTP bearer tokens to individual agent subjects.

Limitations and notes

Vengtoo MCP Gateway MCP server trusts the subject asserted by its own configuration. A reverse proxy or client must not be allowed to choose arbitrary subjects through a forwarded header or untrusted field. For shared HTTP deployments, configure caller token-to-subject mappings and host or origin restrictions as appropriate.

The gateway authorizes calls but does not replace the policies that define access. Local deployments need a running Vengtoo Agent and a Rego policy; cloud deployments need access to Vengtoo Cloud and a valid API key. Downstream MCP servers must be independently configured with their launch command and arguments.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Vengtoo MCP Gateway

Vengtoo MCP Gateway is an MCP server that connects MCP clients to downstream MCP servers through an authorization proxy. Its main functions are intercepting tool calls, checking them with Vengtoo Cloud or a local Vengtoo Agent, forwarding allowed calls, and recording structured audit details such as subjects, tools, arguments, and decisions.

Install it from the published npm package and run it with a JSON configuration. The configuration needs an authorization endpoint, a subject, and downstream server definitions. Node.js 18 or newer is required. Local mode also requires the Vengtoo Agent and a Rego policy file.

Yes. Cursor is named as a supported MCP client in the README. Use the default stdio transport for a local Cursor configuration, or expose the gateway over Streamable HTTP when a remote MCP endpoint is needed.

It checks each tool invocation before forwarding it to the downstream MCP server. The check goes to either a local Vengtoo Agent evaluating a Rego policy or the Vengtoo Cloud API. The policy receives the configured subject and resource information and returns the authorization decision.

Configure caller bearer tokens or anonymous access tokens before binding HTTP to a non-loopback interface. Per-caller mappings can assign separate subjects, while `allowedHosts` and `allowedOrigins` provide DNS-rebinding protection. The gateway rejects an unauthenticated non-loopback setup unless `VENGTOO_GATEWAY_ALLOW_UNAUTHENTICATED=true` is set.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewVengtoo MCP Gateway AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-gateway-2?style=directory)](https://allmcps.com/mcp/mcp-gateway-2)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-gateway-2"><img src="https://allmcps.com/api/badge/mcp-gateway-2?style=directory" alt="Vengtoo MCP Gateway on AllMCPs" /></a>