Skip to main content
Glama
KitchenSink4AI

KitchenSink4Web

Official
by KitchenSink4AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to KitchenSink4Web

No user-submitted related servers found.

    Related Servers

    • Navigator MCP

      Sreehari2011
      A
      license
      B
      quality
      B
      maintenance
      Enables LLM agents to automate web browsers with token-efficient perception, stealth anti-detection, captcha solving, network interception, and isolated persistent sessions.
      51
      MIT

    • antibrowser-mcp

      reacerland
      F
      license
      A
      quality
      D
      maintenance
      Enables LLM agents to browse and interact with web pages using a stealth Chromium browser, with an accessibility-tree interface for low token usage.
      12
      -

    • @tokens/dsh-browser-use

      TokensAPI
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables language models to control a real visible browser with a full set of 24 tools for navigation, clicking, form filling, screenshots, and reading page structure, while preserving login states and supporting configurable browser policies.
      171 npm
      MIT

    • codearia-sieve

      AntonG87
      A
      license
      A
      quality
      A
      maintenance
      Enables agents to parse web pages into decision-ready state—dates as dates, numbers with units, and text chunks sized for a model's window—reducing token usage and providing traceable anchors.
      2
      332 npm
      5
      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

    A3.6/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct jobs, especially session/tab management versus navigation versus monitoring. The only mild overlap is among get_page_view, get_text, and find_elements, but their descriptions specify different output contracts: orientation, prose, and targeted refs.

    Naming Consistency3/5

    Names are readable and semantically grouped, but conventions are mixed: get_* for reads, manage_* for resources, bare verbs like navigate/scroll/wait_for for actions, and find_elements breaks the order. There is no single consistent verb_noun pattern across the set.

    Tool Count5/5

    Twelve tools is well within the ideal range for a web automation/browser server. Each tool covers a distinct aspect of the lifecycle—session, tabs, navigation, reading, searching, waiting, monitoring, and meta-inspection—without obvious redundancy.

    Completeness2/5

    The set is strong on navigation, reading, monitoring, and session management, but there is no click, type, submit, or select tool. get_page_view and find_elements repeatedly return 'refs you can act on,' yet no tool exists to act on them, creating a significant dead end for real web interaction.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources