Sentinel Gateway
Related Servers
Alternatives to Sentinel Gateway
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA 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

evav-gatewayofficial
AlicenseNot gradedqualityBmaintenanceGoverned 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- 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
- AlicenseNot gradedqualityDmaintenanceA defensive gateway and firewall for AI agents using MCP servers, scanning tool calls, responses, and manifests for prompt injection, secrets, dangerous commands, and drift before allowing execution.MIT
- AlicenseNot gradedqualityDmaintenanceA security gateway that enforces policies, tracks data taints, and sandboxes tool calls between AI agents and MCP servers. It provides a secure chokepoint to prevent prompt injection and ensure OWASP ASI compliance through audit logging and deterministic execution.2Apache 2.0
- FlicenseNot gradedqualityCmaintenanceMCP server that provides a security gateway for AI agents, enforcing allow/confirm/deny policies on tool calls and requiring human approval for risky operations, with full audit logging.-
TDQS
Scored across 20 tools
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.
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.
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.
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.