governed-mcp
Related Servers
Alternatives to governed-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProxy for any MCP server that lets read tools pass straight through while turning every write tool into a pending card the agent cannot release on its own. Only signed evidence from the user's paired device — a tap on the approval page or their own transcribed voice — actually executes the action, with one-time nonces, expiry, replay checks and receipts.19 PyPIMIT
- AlicenseAqualityBmaintenanceSecurity-enforcing MCP proxy that sits between an AI agent and any number of downstream MCP servers, intercepting every tool call through a capability-token policy gateway that can allow, deny, or escalate to human approval before the call reaches any real tool. It also exposes built-in operator tools for approval workflows, audit trail queries, token management, voice/HUD output, and hierarchical2115Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides a governance layer for MCP servers, enforcing policy-based allow/deny/approval rules, requiring human approval for risky calls, and recording an auditable trail of every AI agent tool call.MIT
- AlicenseNot gradedqualityCmaintenanceProvides a human-in-the-loop approval gateway for AI agents, enforcing policies and audit logging for MCP-compatible tool calls.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceProvides 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.-
- AlicenseNot gradedqualityBmaintenanceSits in front of any MCP server to enforce allow/ask/block policies on tool calls, paths, shell commands, and network domains, with local approval prompts and an audit log.MIT
TDQS
Scored across 9 tools
Each tool maps to a distinct resource+action: searching vs. fetching tickets, commenting vs. updating status, refunding, and deleting a customer are all clearly separated. The only mild overlap is between list_pending (all held calls) and approval_status (one call by id), but the descriptions make the boundary readable.
Strong, predictable snake_case verb_noun pattern (search_tickets, get_ticket, add_comment, update_ticket, issue_refund, delete_customer). The two approval tools deviate slightly toward noun phrasing (list_pending, approval_status), with approval_status notably lacking a verb.
Nine tools is well within the ideal 3-15 range and each one earns its place across the ticket, customer, and approval-gate surfaces. No tool looks redundant or vestigial.
Read/update/comment/refund/delete are covered, but there is no create_ticket and no customer creation or update, so the lifecycle is not closed. The approval flow also lacks any approve/deny operation, leaving agents to rely on an out-of-band human decision.