Skip to main content
Glama
webuplink-dev

@webuplink/mcp

by webuplink-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @webuplink/mcp

No user-submitted related servers found.

    Related Servers

    • Cloudflare Playwright MCP

      xvv6u577
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control a browser through a set of tools, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.
      -

    • Cloudflare Playwright MCP

      q275212
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control a browser through a set of tools, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.
      -

    • Cloudflare Playwright MCP

      AI24K
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control a browser through a set of tools, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.
      -
    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

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: browse handles opening or continuing a session and interacting with pages, while close_session explicitly handles teardown and resource cleanup. There is no overlap between them, so an agent should not confuse which tool to call.

    Naming Consistency4/5

    Both tool names use imperative verbs, which is coherent, but browse is a bare verb while close_session follows a verb_noun pattern. The inconsistency is minor given the very small tool set, but a more consistent name like browse_page would improve the pattern.

    Tool Count3/5

    At two tools, the server feels thin for what appears to be a web browsing or browser automation domain. The two tools do form a minimal session lifecycle, so the count is borderline rather than obviously wrong, but it likely underrepresents the full range of browsing actions an agent might need.

    Completeness3/5

    The core lifecycle of opening/continuing a session with browse and closing it with close_session is covered, but there is no explicit session listing or status tool, and the browse tool appears to absorb many possible page actions into one generic entry point. Agents may be able to work around the gaps, but the surface is notably sparse for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources