# Vengtoo MCP Gateway [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://github.com/authzx/mcp-gateway  
**GitHub Stars:** 0  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-gateway-2

## Description
AuthzX MCP Gateway — policy-enforcing proxy between AI agents and MCP servers

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "vengtoo-mcp-gateway": {
    "command": "npx",
    "args": ["-y","vengtoo-mcp-gateway"]
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/mcp-gateway-2/readme_

