Skip to main content
Glama
xxxbrian

MCP-RQuest

by xxxbrian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MCP-RQuest

No user-submitted related servers found.

    Related Servers

    • URL Fetch MCP

      aelaguiz
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that enables Claude or other LLMs to fetch content from URLs, supporting HTML, JSON, text, and images with configurable request parameters.
      3
      3
      MIT
    • Crawlbase MCP by crawlbase

      Crawlbase MCPofficial

      crawlbase
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to fetch live web content with JavaScript rendering, proxy rotation, and anti-bot evasion.
      9
      83 npm
      58
      MIT

    • Puppeteer-Extra MCP Server

      gpaul-faldin
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides enhanced browser automation capabilities using Puppeteer-Extra with Stealth Plugin, enabling LLMs to interact with web pages in a way that better emulates human behavior and avoids detection as automation.
      3
      MIT
    • BrowserCat MCP Server (Browser Automation) by browsercat

      BrowserCat MCP Server (Browserofficial

      browsercat
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides browser automation capabilities using BrowserCat's cloud browser service. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment without needing to install browsers locally.
      7
      11 npm
      6
      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

    B3.2/5.0

    Scored across 12 tools

    Disambiguation4/5

    The HTTP method tools are clearly distinct, and the two stored response tools are differentiated by markdown conversion. However, get_stored_response and get_stored_response_with_markdown could be confused by an agent without careful reading, but descriptions mitigate ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern, with http_ prefix for HTTP methods and clear action words like get, restart, and retrieve. The naming is highly predictable and uniform.

    Tool Count5/5

    12 tools is well-scoped for an HTTP client with model management and stored response retrieval. Each tool has a clear purpose, and the count is neither sparse nor overwhelming.

    Completeness4/5

    The HTTP methods cover all standard request types, and stored response handling is present. Minor gaps include no tool to clear or list stored responses, and model state tools are limited to get and restart, but core functionality is complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources