Skip to main content
Glama
spliffspliff70-wq

websense

by spliffspliff70-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to websense

No user-submitted related servers found.

    Related Servers

    • Fast Browser MCP

      kqlio67
      A
      license
      C
      quality
      A
      maintenance
      Enables AI agents and developers to automate real Chrome/Chromium browsers through the Chrome DevTools Protocol, with token-efficient snapshots, multi-action batching, shadow DOM traversal, system-page control, extension management, and network/WebSocket inspection.
      64
      MIT

    • agent-browser-mcp

      335234131
      A
      license
      B
      quality
      F
      maintenance
      Enables AI agents to directly control your real Chrome browser with full context including login sessions, cookies, and open tabs. It provides tools for page scanning, JavaScript execution, CDP control, screenshots, and physical mouse/keyboard input for authentic browser automation.
      20
      243
      MIT

    • live-mcp

      ghien-dev
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to declaratively control web pages using real mouse and keyboard events via Chrome DevTools Protocol, without executing page JavaScript.
      11 npm
      1
      -

    • AgentBrowser

      AshtonVaughan
      F
      license
      Not graded
      quality
      B
      maintenance
      A semantic browser runtime for AI agents that replaces raw HTML with structured data and dynamic, page-specific tools. It features built-in site memory and automated bot detection bypass to enable efficient, self-healing web automation.
      1
      -
    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.9/5.0

    Scored across 28 tools

    Disambiguation3/5

    Several tools overlap in action space: 'click' and 'real_click' both click at viewport coordinates, and 'real_activate_tab' overlaps with tab switching. However, the descriptions do clarify the mechanism differences well enough that an agent can usually pick the right tool.

    Naming Consistency2/5

    Naming is inconsistent: verb_noun names like 'explore_page' and 'type_text' sit alongside bare verbs like 'read', 'click', and 'wait', plus bare nouns like 'tabs', 'cookies', and 'session'. The 'real_' prefix is only used on three tools, adding to the lack of a predictable pattern.

    Tool Count2/5

    With 28 tools, the server exceeds the 25-tool threshold for 'too many'. Several tools are narrow lifecycle or debugging helpers, such as 'respawn_offscreen', 'extension_reload', and 'websense_guide', which inflate the surface without adding distinct user-facing capabilities.

    Completeness5/5

    The tool set thoroughly covers the browser-automation lifecycle: navigation, reading, clicking, typing, forms, scrolling, waiting, tabs, dialogs, cookies, console/network logs, screenshots, and JS evaluation. There are no obvious dead ends for common agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources