mcp-gatehouse
Related Servers
Alternatives to mcp-gatehouse
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA least-privilege enforcement proxy for MCP servers. It sits between MCP clients and upstream servers, enforcing tool policies, hiding denied tools, requiring human approval for risky actions, and providing a structured audit trail.MIT
- AlicenseNot gradedqualityBmaintenanceEnforces identity-based access control and audit logging for MCP servers, letting you grant fine-grained tool permissions to users and systems while failing secure by default.MIT
- AlicenseNot gradedqualityCmaintenanceEnables developers to expose any dev tool as a safe, audited MCP server with permission tiers, audit logging, and automatic argument validation.MIT
- AlicenseAqualityBmaintenanceA security-first MCP server for managing Whatbox slots with structured read-only inspection and approval-gated mutations, including storage, services, website deployment, and torrent control.30MIT
- AlicenseNot gradedqualityBmaintenanceEnables developers to scaffold secure-by-default MCP servers with deny-all permissions, typed tool stubs, and pre-wired audit hooks, while enforcing security posture through CI.0MIT
- AlicenseBqualityBmaintenanceLocal MCP server for inspecting and managing an allowlisted Discord server via Discord's REST API, with safety modes, idempotent JSON blueprints, and destructive-operation safeguards.271MIT
TDQS
Scored across 4 tools
Each tool targets a distinct action and the descriptions explicitly cross-reference each other (add_note vs cancel_order, list_orders vs lookup_order). There is no realistic way to misselect among these four.
All four names follow a clean verb_noun snake_case pattern: add_note, cancel_order, list_orders, lookup_order. The verbs (add/cancel/list/lookup) are distinct and predictable.
Four tools is a bit lean but well-matched to a gatehouse control surface (observe, annotate, cancel). Each tool earns its place with no redundant or filler operations.
The surface covers the read (list_orders, lookup_order) and controlled-write (add_note, cancel_order) lifecycle cleanly. Order creation and non-cancellation status updates are absent, but these are plausibly out of scope for a gatehouse desk.