Skip to main content
Glama

Related Servers

Alternatives to brydge-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      7
      182 PyPI
      4
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides permission gates and tamper-evident audit logging for AI agent tool executions, with declarative policies, consent ladders, and hash-chained verification.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to request human approval before consequential actions, with policy-based routing, phone-based approver decisions, and signed audit evidence.
      351 npm
      MIT

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues