Skip to main content
Glama

Related Servers

Alternatives to Mcp-Warden

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Local credential broker that enables AI agents to securely run CLI tools like SSH and MySQL without exposing passwords to the AI context, environment variables, or process listings.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI agents make authenticated API and OAuth calls using stored credentials they never see, with per-credential Touch ID approval, proxy execution, and a local audit log of every use.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Self-hosted credential store and API proxy for AI agents. One Bearer token, all your services. Handles OAuth refresh, encrypted storage, audit logging, and per-agent permissioning.
      79 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Local zero-trust permission gateway for AI agents. Enforces policy-based tool authorization, human approvals, scoped permissions, and cryptographically verifiable audit logs.
      4
      128 PyPI
      5
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to make authenticated HTTP requests and run shell commands by writing placeholder tokens instead of real credentials, with values resolved locally from the macOS Keychain and responses scrubbed so secrets never enter the chat. It also supports per-client scoping, host-locking, and an audit log of key usage.
      25 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Credential isolation proxy for AI agents. Injects API keys at the network boundary so your agent never sees the raw credential. Supports domain allowlists, agent auth, policy enforcement, and audit logging.
      3
      79 npm
      16
      Apache 2.0

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools target clearly distinct resources: HTTP via presets, SFTP transfer, named DB queries, secret reveal, and preset listing. The one fuzzy pair is ssh_exec (allow-listed shell command) vs ssh_run (preset-declared named command), which both execute on the same host and could be confused despite the descriptions drawing the distinction. Overall the boundaries are clear, with that single adjacent pair.

    Naming Consistency4/5

    All names are snake_case and readable, using recognizable domain nouns (db, ssh, sftp, http, secret, presets). The ordering is mixed — noun_verb in db_query/sftp_transfer/ssh_exec/ssh_run/proxy_http versus verb_noun in get_secret_for_env/list_presets — which is a minor deviation rather than a real inconsistency.

    Tool Count5/5

    Seven tools is well-scoped for a credential/action broker: one discovery tool, one per transport (HTTP, SSH exec, SSH named, SFTP, DB), plus an escape hatch for secrets. Each tool clearly earns its place and nothing looks redundant.

    Completeness3/5

    Core action paths are covered, but discovery has a real hole: db_query requires a `query_name` yet list_presets is documented as returning named commands only for SSH presets, so an agent may not be able to learn valid DB query names. The audit log is referenced on nearly every tool but there is no way to read it, and no tool surfaces or manages approval windows.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data