Skip to main content
Glama
hotlogin-browser

hotlogin-mcp

by hotlogin-browser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to hotlogin-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Browser

      wgarrido
      A
      license
      A
      quality
      D
      maintenance
      MCP server that lets AI assistants browse the web through your real Chrome with your cookies, sessions, and fingerprint, avoiding bot detection and CAPTCHAs. Enables web browsing, content extraction, and multi-step workflows via persistent tabs.
      15
      1 npm
      3
      MIT

    • browser-store

      bysking
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing and controlling multiple isolated Chrome/Edge browser instances, exposing tools for navigation, screenshots, clicking, form filling, and JavaScript execution to AI clients.
      3 npm
      MIT

    • scout-mcp-server

      stemado
      A
      license
      A
      quality
      B
      maintenance
      MCP server for browser automation with anti-detection. Scout pages, find elements, interact with websites, and monitor network traffic from any AI client that supports the Model Context Protocol.
      21
      1
      MIT
    • GoLogin MCP by gologinapp

      GoLogin MCPofficial

      gologinapp
      A
      license
      C
      quality
      D
      maintenance
      Manage your GoLogin browser profiles and automation directly through AI conversations. This MCP server connects to the GoLogin API, letting you create, configure, and control browser profiles using natural language.
      59
      76 npm
      22
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.7/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. Tools are organized by resource type (env, group, proxy, health) and specific actions (create, query, remove, revise, etc.), making it easy for an agent to select the right tool without confusion.

    Naming Consistency5/5

    Tool names follow a highly consistent pattern throughout: resource_action format (e.g., env_create, group_query, proxy_remove). All tools use snake_case with no deviations, and verbs are standardized across resources, ensuring predictable naming.

    Tool Count4/5

    With 23 tools, the count is slightly high but reasonable for the server's scope of managing environments, groups, and proxies. Each tool appears to earn its place by covering specific operations, though it may feel heavy compared to simpler servers.

    Completeness5/5

    The tool surface provides complete CRUD/lifecycle coverage for environments, groups, and proxies, including additional operations like launching, terminating, and checking health. There are no obvious gaps, and agents can handle full workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources