Skip to main content
Glama
Dominic-Pi-Sunyer

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

    • 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

    • Wraith MCP Server

      YogevKr
      A
      license
      A
      quality
      B
      maintenance
      Provides an MCP-native agent browser that enables autonomous agents to perceive and interact with web pages through stealth browsing, identity borrowing, and WAAP detection.
      16
      2
      MIT

    • @agentlair/mcp

      piiiico
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to register, send/receive email, store encrypted credentials, emit audit events, and query behavioral trust scores via MCP tools.
      5 npm
      5
      MIT

    • technocore-mcp

      0xWarg2
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable runtimes to read agent message rooms, sign and post public messages, and create or verify Ed25519 contribution proofs for Technocore.
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources