Governed Mcp Gateway

io.github.icohangar-opsPublished by GitHub account icohangar-opsv0.1.0Updated Oct 25, 2026

HTTP MCP gateway: principal on tools/call + SSE, allowlists, vault rotate, CHP gates.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local HTTP MCP gateway that fronts other MCP servers with principal checks on tool calls, allowlists, vault rotation and CHP gates.

What you can do
  • Acts as an HTTP/SSE gateway in front of MCP servers rather than exposing its own domain tools.
  • Applies a principal identity to tools/call requests and serves clients over SSE.
  • Enforces allowlists to control which tools or targets are permitted.
  • Supports vault rotation for managed secrets.
  • Applies CHP gates as an additional policy checkpoint.
  • No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Worth considering when you run several MCP servers locally and want a single governed entry point that identifies callers, restricts what they may call, and rotates credentials. Less useful for a single personal server with no access-control needs.
Requirements
Runs as a local process on the user's machine (desktop only, not web-executable), distributed as the npm package @cubiczan/governed-mcp-gateway with SSE transport, so a Node.js runtime is implied. No authentication, environment variables or headers are declared in the manifest.
Before you install
It sits in the path of tool calls and can block or permit them, so a misconfiguration affects every server behind it. It manages a vault and credential rotation, meaning secrets pass through it. No authentication is declared, so check how the HTTP/SSE endpoint is bound and who can reach it before exposing it beyond localhost.

Installation

In SourceWeft

  1. Open Governed Mcp Gateway in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts