brydge-mcp
Related Servers
Alternatives to brydge-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to propose changes, obtain human or policy approval, and safely apply them with drift checks, idempotency, verified completion, compensation, and a tamper-evident ledger.651 npmMIT
- AlicenseBqualityBmaintenanceEnables AI agents to execute actions under an accountability layer with identity passports, mandates, a permission gate, and a tamper-evident journal, while requiring human confirmation for irreversible operations.776 PyPI5AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI agents to safely act on business backends by enforcing per-agent permissions, autonomy thresholds, human approval with review-and-edit, and full audit trails.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to run side-effecting actions like tool calls, file writes, and payments only when each exact set of arguments is covered by a signed, scoped, single-use permit verified server-side, with high-risk actions requiring human sign-off and every allow/deny recorded in a tamper-evident hash-chained ledger.4-
- AlicenseBqualityCmaintenanceEnables AI agents to act on live business objects under enforceable per-call identity, per-tool grants, and mandatory human approval for irreversible actions, with connectors isolated from core logic.8MIT
- AlicenseNot gradedqualityCmaintenanceProvides permission gates and tamper-evident audit logging for AI agent tool executions, with declarative policies, consent ladders, and hash-chained verification.MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: supervise (request permission), report_outcome (report results), verify (check actual state), get_finding (retrieve stored findings), and get_headroom (check quota). No two tools overlap in function; an agent can easily select the right one based on the action needed.
All tools follow a consistent 'brydge_' prefix with a verb or verb_noun pattern (e.g., supervise, report_outcome, verify, get_finding, get_headroom). The naming is uniform, predictable, and clearly indicates the action each tool performs.
With only 5 tools, the server is well-scoped to its domain of permission, reporting, verification, and quota management. Each tool earns its place and together they cover the core workflow without unnecessary bloat.
The tool surface covers the full lifecycle: request permission (supervise), report outcome (report_outcome), verify actual state (verify), retrieve past findings (get_finding), and check limits (get_headroom). No obvious gaps exist for the stated purpose.