Skip to main content
Glama
sposer

mcp-fetch

by sposer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-fetch

No user-submitted related servers found.

    Related Servers

    • Simple MCP Server

      yuandabo
      A
      license
      Not graded
      quality
      C
      maintenance
      A minimal MCP server providing tools for time, calculations, sandboxed file operations, and safe URL fetching over stateless HTTP.
      5 npm
      ISC

    • Homelab MCP starter

      sailfact
      F
      license
      Not graded
      quality
      B
      maintenance
      A minimal MCP server for homelab environments, providing demo tools like ping and echo over Streamable HTTP for testing client-server integration.
      -

    • MCP API Requester

      yryuu
      F
      license
      A
      quality
      D
      maintenance
      An MCP server that enables LLMs to make arbitrary HTTP requests (GET, POST, PUT, DELETE, etc.) with custom headers, bodies, and cookies, supporting JSON and error handling.
      1
      2
      -

    • fetch-url-raw

      cinit
      A
      license
      Not graded
      quality
      B
      maintenance
      A stateless MCP server that provides a configurable HTTP client tool for LLM agents, supporting custom methods, headers, bodies, timeouts, redirects, response size limits, DNS overrides, and TLS verification.
      MIT

    • remote-mcp

      sch246
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets you execute commands, manage files, run persistent shell sessions, transfer large files, and control background processes on remote machines via a lightweight HTTP agent, useful when SSH/WinRM/SMB are unavailable.
      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.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: fetch_page is for scraping dynamic web pages with JavaScript rendering and converting to Markdown, while http_request is for generic HTTP requests to APIs or raw files. The descriptions explicitly note when to use each tool, eliminating any overlap or confusion.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (fetch_page and http_request) with clear, descriptive names that match their functions. There are no deviations or mixed conventions in the naming style.

    Tool Count3/5

    With only 2 tools, the server feels thin for a general-purpose HTTP fetching domain, as it might lack coverage for specialized scenarios like WebSocket handling or advanced caching. However, the tools cover core use cases (dynamic page scraping and generic HTTP requests), making it borderline but functional.

    Completeness4/5

    The tool set covers essential HTTP operations for web scraping and API interactions, with clear guidance on when to use each tool. Minor gaps exist, such as no dedicated tools for WebSocket connections or batch request handling, but agents can likely work around these using the provided tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources