Skip to main content
Glama
Sign In
Sentinel Gateway

Sentinel Gateway

by jaisimha18
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Sentinel Gateway

No user-submitted related servers found.

    Related Servers

    • ToolBastion

      MaharMuavia
      A
      license
      Not graded
      quality
      C
      maintenance
      A zero-trust security gateway for MCP tool calls, inspecting tool identity, arguments, execution decisions, and returned content before risk reaches your coding agent.
      Apache 2.0

    • citadel

      rephuren
      A
      license
      Not graded
      quality
      B
      maintenance
      A security gateway that sits between an MCP client and real MCP servers, routing every tool call through namespace isolation, definition pinning, argument and rate policies, taint tracking, and response injection checks. It blocks tool shadowing, rug pulls, hidden Unicode payloads, path traversal, and exfiltration of private data to outside channels, while logging each decision and requiring out-of-band human approval for sensitive calls.
      19 npm
      2
      MIT
    • evav-gateway

      evav-gatewayofficial

      evavai
      A
      license
      Not graded
      quality
      D
      maintenance
      Governed MCP gateway that lets AI agents call tools with policy enforcement, prompt-injection screening, a kill-switch, and tamper-evident signed audit logs.
      Apache 2.0

    • MCP Warden

      dnanatihor
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to reach upstream MCP tool servers through a central policy gateway that authenticates each agent, enforces least-privilege and default-deny rules, and applies response obligations such as redaction, inference stripping, PII masking, and truncation. It also records every decision in a tamper-evident, hash-chained audit log that can be verified later.
      Apache 2.0
    • Proofpane

      Proofpaneofficial

      Proofpane
      A
      license
      B
      quality
      A
      maintenance
      A 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.
      13
      MIT

    • Bulwark

      claudius-ars
      A
      license
      Not graded
      quality
      D
      maintenance
      Acts as an MCP gateway between AI agents and upstream tool servers, evaluating YAML policies on every tool call, injecting real credentials at the last mile, scanning requests and responses for secrets, PII, and prompt injection, and recording each action in a tamper-evident audit log. Also supports HTTP forward-proxy governance with rate limiting, cost tracking, and policy replay against historical audit data.
      4
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 20 tools

    Disambiguation4/5

    Tools are largely distinct, each targeting a specific operation: registration, RBAC policies, ledger queries, review queue, demo setup, attacks. However, sentinel_call_tool, sentinel_get_call_history, and sentinel_run_full_demo have some conceptual overlap (all involve executing calls), and the demo/attack/reset tools blur boundaries for agents trying to pick between setup, run, and attack flows.

    Naming Consistency4/5

    All tools follow a consistent sentinel_[verb]_[noun] pattern with snake_case throughout, which is excellent. Minor inconsistency exists with get_dashboard_stats vs get_call_history (both use 'get') and the setup tools using 'setup' vs 'run' verbs that could be more uniform, but the pattern is strongly predictable overall.

    Tool Count3/5

    At 20 tools, this sits at the upper edge of the acceptable range. The core security pipeline (register, list, policy, call, ledger, review) is about 12 tools, but the demo helpers (setup_demo, setup_demo_policies, run_full_demo, reset_demo, run_attack) add 5 tools that are more for demonstration than real operation, inflating the count beyond what a production gateway would need.

    Completeness4/5

    The surface covers the full security workflow: server registration, RBAC management, call routing, ledger querying/integrity, review queue with approve/deny, and attack simulation. Minor gaps include no tool to unregister/remove a server, and no tool to view all agents' detailed permissions in one place, but the core lifecycle is largely complete.

    Resources