Skip to main content
Glama

Related Servers

Alternatives to Auth Your Agent

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Lets Claude Code drive a real Google Chrome while you watch a low-latency live view and take over the mouse and keyboard whenever a login, CAPTCHA or payment appears. Sensitive actions pause for phone-based approval, and the agent can be guided by tapping elements or sending short messages without exposing secrets.
      32 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI assistants control your real Chrome browser to perform web tasks like reading pages, taking screenshots, clicking, and typing, using your existing logged-in sessions.
      133
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Zero-knowledge credential injection for AI agents. Your agent authenticates to websites and APIs without ever seeing a password, TOTP code, or API key.
      10 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to drive a privacy-first browser via MCP, using diff-based page observation to reduce token consumption, and offering secure autofill from a local vault.
      2,181 npm
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Gives agents an autonomous browser that takes a single goal-level call and drives a real Chrome step by step, returning a verified result or a concrete question instead of guessing. It keeps passwords out of prompts, requires approval before buy/pay/delete actions, and detects login walls and bot challenges.
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to securely control a real, logged-in browser with per-site permissions, per-action approvals, secret redaction, and a tamper-evident audit log, all locally without a cloud relay.
      415,293 npm
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target clearly distinct operations (navigate vs click vs type_text vs read_page vs fill_secret). The takeover cluster (check_login_wall, request_takeover, wait_for_takeover) and the two check_* tools risk minor confusion, but the descriptions explicitly explain how they chain together.

    Naming Consistency4/5

    Strong snake_case, verb-first convention throughout (list_secrets, fill_secret, read_page, end_session, request_approval, request_takeover). Only minor deviations: bare-verb browser tools (navigate, click) and the verb_prep_noun form of wait_for_takeover, which still stay readable and predictable.

    Tool Count5/5

    13 tools is well within the ideal 3-15 range and each one earns its place: browser control, secret filling, the login/takeover lifecycle, approval, session teardown, reporting and status all cover distinct needs without redundancy.

    Completeness4/5

    The set covers the full auth-agent lifecycle: authorization check, browsing actions, secret filling, login-wall detection, owner takeover, approvals, session cleanup and issue reporting. Minor gaps exist (e.g. no explicit scroll, back-navigation or screenshot), but core agent workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues