Skip to main content
Glama
Sign In
web-speed-agent

web-speed-agent

by Dominic-Pi-Sunyer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to web-speed-agent

No user-submitted related servers found.

    Related Servers

    • Cursor Cloud MCP

      BenItBuhner
      A
      license
      C
      quality
      C
      maintenance
      Enables any MCP client to triage cloud agents, projects, conversations, transcripts, pull requests, and files, including listing agents, reading transcripts, following runs, and sending follow-ups, using an API key or browser sign-in.
      29
      MIT

    • ChatGPT Gateway MCP Nyan

      wada-qualia
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agent clients to safely connect to tools and execution resources through MCP with authorization, approvals, audit, chat-context isolation, SSH/Docker access, and long-running command session tracking.
      MIT

    • Attenza

      maxhillaert
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides OAuth-based MCP integration and client-side tooling for connecting agents to a remote service, with CLI and plugin support.
      MIT

    • keyhall

      luizgustavosaraiva
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to access remote and local MCP servers plus HTTP APIs through a single MCP endpoint, with per-consumer scoped tokens, tool-level permissions, and encrypted secret management.
      5
      AGPL 3.0

    • cleanslop

      cleanslop
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to start and monitor scans of pushed commits, read findings worst-first, compare reports, redeem scan credits, and exchange feedback through an authenticated remote MCP connection.
      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

    A4.2/5.0

    Scored across 24 tools

    Disambiguation4/5

    Tools largely target distinct actions (navigate, click, fill_field, hover, scroll, select_option), and the wait tools are separated by what they wait for (element vs predicate vs URL). Minor overlaps exist—submit_form can be achieved with click or press_keys, and login overlaps with fill_field+submit_form—but descriptions clearly delineate these cases.

    Naming Consistency5/5

    All tool names use consistent snake_case with verb-first semantics (store_credential, fill_field, wait_for_url, get_page_info, close_browser). Single-word verbs like navigate/click/hover/scroll remain within the same predictable style, so the surface reads uniformly.

    Tool Count4/5

    24 tools is on the heavier side for the rubric, but browser automation inherently spans navigation, interaction, waiting, credential management, browser lifecycle, and Workspace editing—each tool does appear to earn its place. No obvious redundant tools, so it lands slightly over rather than bloated.

    Completeness4/5

    The surface covers a full lifecycle: browser setup/open/close, navigation, interaction, multiple wait primitives, form handling, page reading, JS evaluation, and credential storage. Gaps like screenshots, tab/window management, and file upload/download exist but are workable around, especially via evaluate.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources