evav-gateway
OfficialProvides governed access to Slack's MCP server, allowing AI agents to interact with Slack workspaces through a policy-checked, injection-screened proxy with signed audit logging.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@evav-gatewayWhat tool calls were blocked by policy today?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
evav-gateway
The open-source governed MCP gateway. Point any AI agent (Claude, Cursor, ChatGPT, your own) at one endpoint; every tool call it makes is governed — policy-checked, screened for prompt-injection/exfiltration, haltable by a kill-switch — and written to a signed, tamper-evident audit log before it reaches the real tool.
Built on FastMCP for the wire (federation, pooled sessions, auth, transport); the governance layer is ours.
Status: v0.1, early. The governed proxy + signed audit + injection screening work and are tested. OAuth brokering, an OPA policy backend, the one-command client-setup, and packaging are on the roadmap below.
Why
Every OSS MCP gateway governs the wire. Most log unsigned, have no native injection screening, and no approval gate. evav-gateway:
Signs its audit log (Ed25519, hash-chained) — tamper-evident. No surveyed gateway does this.
Screens every call for prompt-injection / exfiltration on the way in and the way out — native, not a bolt-on.
Fails closed: a policy error, an injected argument, a poisoned upstream output, or an engaged kill-switch stops the call. It never silently allows.
Related MCP server: mcp-guardian
Governance pipeline (per tool call)
kill-switch → policy (block / require-approval) → injection screen (input)
→ forward to upstream (pooled session) → injection screen (output, withhold)
→ signed audit recordUse as a library
from fastmcp import Client
from evav_gateway import build_gateway, Policy
gw, audit = build_gateway(
{"mcpServers": {"slack": {"url": "https://mcp.slack.com/mcp"}}},
policy=Policy(approval_tools=("payments.transfer",),
block_patterns=(r"\bssn\b",)),
)
# every call through `gw` is governed; audit.verify() checks the signed chainConfig-as-code
# evav-gateway.yaml
name: "Acme Gateway"
injection_on: true
upstreams:
- name: slack
url: https://mcp.slack.com/mcp
auth_env: SLACK_MCP_TOKEN # secret from env, never inlined
policy:
approval_tools: [payments.transfer]
block_patterns: ["\\bssn\\b", "password"]
param_limits:
payments.transfer: { amount: 1000 }evav-gateway run --config evav-gateway.yamlQuickstart
pip install evav-gateway # or: uvx evav-gateway ...
cp evav-gateway.example.yaml evav-gateway.yaml # edit upstreams + policy
evav-gateway run --config evav-gateway.yaml # serves http://127.0.0.1:8000/mcp
evav-gateway client-setup --client cursor --url http://127.0.0.1:8000/mcp # point your agent hereOr with Docker:
docker build -t evav-gateway .
docker run -p 8000:8000 -v "$PWD/evav-gateway.yaml:/config/evav-gateway.yaml" evav-gatewayRoadmap
Governed proxy on FastMCP (policy · injection in/out · kill-switch · signed audit)
evav-gateway client-setup— one command to point Claude/Cursor/VS Code/Windsurf hereDocker image +
uvx/pip installOPA (Rego) policy backend for enterprise param/context authz (opt-in; see
examples/policy.rego)Brain-injection: inject the org's rules/skills into any agent (
evav_rules/evav_skill)Persistent signed audit (SQLite + stable key) — retrieve via
evav_audit, verify offline viaevav-gateway verify-auditHardened injection screen (decode pass: base64/URL/control-char obfuscation)
OAuth 2.1 + upstream token brokering (agents never hold upstream creds)
Shared multi-replica audit (Postgres + shared key)
Async endpoint + tuned connection pooling under load
Rule/skill/memory context injection (inject the org's relevant rules into any agent)
Helm chart
License
Apache-2.0.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Zero-secret MCP gateway for AI agents: risk-scored, audited calls with human-in-the-loop approval.
MCP gateway with runtime security policy, tool-call-level control, and audit of agent actions.
Zero-trust gateway for AI agents: score tool calls, verify agent cards, enforce policy, audit.
Security gateway for AI agents: policy, approval, and audited execution, no secrets shared.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceA secure MCP gateway for enterprise AI tool execution, enabling governed invocation of business tools with authentication, RBAC, audit logging, PII redaction, and async processing.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA gateway that enforces permissions, sanitization, approval, and audit for AI agent MCP tool calls, with a policy engine and local proxy CLI.1481MIT
- AlicenseBqualityAmaintenanceA governance proxy for AI tools — every MCP/agent tool call is policy-gated, secret-redacted, and written to a hash-chained, offline-verifiable audit trail.13MIT
- FlicenseNot gradedqualityBmaintenanceProvides a secure MCP boundary for AI agents, intercepting and validating tool calls, redacting secrets, and requiring human approval for sensitive actions with a tamper-evident audit trail.-
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/evavai/evav-gateway'
If you have feedback or need assistance with the MCP directory API, please join our Discord server