safe-mcp-bridge-v2
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
safe-mcp-bridge-v2
A fail-closed policy boundary between local stdio MCP clients and authenticated Streamable HTTP servers.
MCP's authorization standard answers who may connect. This bridge adds a local enforcement layer for what an agent may call and what must never leak through the bridge's logs or output.
It translates newline-delimited stdio JSON-RPC into MCP 2026-07-28 Streamable HTTP, injects credentials only at the outbound boundary, mirrors required routing metadata into HTTP headers, applies a local tool policy before network access, and fails closed on secret-shaped upstream output.
Why this still exists after MCP OAuth
OAuth, CIMD, scopes, and protected-resource metadata are essential remote authorization primitives. They do not replace:
per-agent local allowlists;
a conservative read-only mode;
proof that blocked calls never reach the upstream server;
redacted audit trails;
leak fixtures for wrapper and gateway behavior;
env-to-header credential isolation for local stdio clients.
safe-mcp-bridge-v2 is deliberately a narrow safety boundary, not another general MCP platform.
Related MCP server: turnstile
MCP 2026-07-28 support
stateless, self-describing requests with
_metaprotocol/client fields;required
MCP-Protocol-Version,Mcp-Method, andMcp-Nameheaders;spec Base64 sentinel encoding for non-ASCII or unsafe header values;
configured
Mcp-Param-*mirroring forx-mcp-headerdeployments;application/jsonand request-scopedtext/event-streamresponses;transparent MRTR
InputRequiredResultpass-through;202 Acceptednotification handling;explicit rejection of legacy session initialization;
fail-closed header/body and protocol-version checks.
See Compatibility for the exact support boundary.
Quick start
git clone https://github.com/efe-arv/safe-mcp-bridge-v2.git
cd safe-mcp-bridge-v2
uv sync --extra dev
cp examples/modern-read-only.yaml bridge.yamlSet the credential named by auth.env without placing it in YAML:
export EXAMPLE_MCP_TOKEN='use-your-secret-manager-here'
uv run safe-mcp-bridge-v2 doctor bridge.yaml
uv run safe-mcp-bridge-v2 run bridge.yamlExample stdio input:
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"memory.search","arguments":{"query":"status"}}}The bridge adds modern MCP metadata and sends headers equivalent to:
MCP-Protocol-Version: 2026-07-28
Mcp-Method: tools/call
Mcp-Name: memory.search
Authorization: Bearer <injected at runtime>Credentials are never included in audit records.
Policy modes
Allowlist
Only explicitly named tools may cross the network boundary:
policy:
mode: allowlist
allow_tools:
- memory.search
- memory.readRead-only
Blocks tool names containing write-shaped segments such as create, delete, send, update, or write:
policy:
mode: read_onlyRead-only name matching is a conservative local guard, not semantic proof. Prefer an allowlist for consequential environments.
x-mcp-header deployments
The 2026-07-28 HTTP binding can mirror selected primitive tool arguments into Mcp-Param-* headers. Configure mappings learned from your server's tool schema:
protocol:
custom_tool_headers:
execute_sql:
region: Region
tenant.id: TenantThe bridge performs spec-compliant primitive conversion and Base64 sentinel encoding. Automatic schema discovery is intentionally not in 0.1.0; mappings are explicit and auditable.
Commands
safe-mcp-bridge-v2 doctor CONFIG
safe-mcp-bridge-v2 run CONFIG
safe-mcp-bridge-v2 policy-check CONFIG METHOD [--tool TOOL]
safe-mcp-bridge-v2 leak-scan PATHVerification
uv run ruff check .
uv run mypy
uv run pytestCI runs the same checks on Python 3.11 and 3.12, plus dependency and secret scanning.
Security model
Read SECURITY.md and Threat model before deployment. Important boundaries:
redaction is defense in depth, not encryption;
upstream authorization and data minimization remain mandatory;
an allowlist cannot make a malicious upstream safe;
this bridge does not terminate an OAuth browser flow in
0.1.0;legacy stateful MCP sessions require a separate compatibility adapter;
local process compromise remains outside the bridge's protection boundary.
Origin
This is a clean second-generation implementation of the original private safe-mcp-bridge, rebuilt for the MCP 2026-07-28 stateless protocol. Created by Efe Büken / Arven Digital.
License
Apache-2.0. See LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Streamable HTTP MCP gateway for NV oOS fleets — one API key, namespaced tools, quotas and policy.
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables developers to wrap existing MCP servers with a deterministic policy enforcement gate that intercepts tool discovery and tools/call requests over stdio, allowing only authorized calls to reach the downstream server. It supports dynamic tool exposure or hiding, allow/deny/approval-required decisions, configurable error disclosure modes, and Ed25519-signed retry credentials for approved workflows.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnforces default-deny policies, budgets, and tamper-evident audit logging for MCP tool calls before they reach upstream servers.-
- AlicenseNot gradedqualityBmaintenanceA policy-enforcing sandbox proxy that sits between an agent and an upstream MCP server, letting tool visibility, file paths, hostnames, credentials-looking arguments and timeouts be governed by a single TOML policy file before anything reaches the server. It exposes only the allowed tools, rejects disallowed calls with readable reasons, and writes one audit line per decision without logging argument values.MIT
- AlicenseAqualityBmaintenanceLocal execution gate and stdio MCP proxy for AI agents, with tool policies, expiring leases, approvals and operator kill. Starts with two read-only setup tools; protection requires a trusted downstream server and private operator configuration. Not an OS sandbox. Apache-2.0.247 PyPI6Apache 2.0