Skip to main content
Glama
jialinhome

page-fetcher-mcp

by jialinhome
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to page-fetcher-mcp

No user-submitted related servers found.

    Related Servers

    • ax-mcp

      cawa0505
      F
      license
      A
      quality
      B
      maintenance
      MCP server for remote web scraping, providing a scrape_web tool that fetches pages and extracts content as markdown or JSON, supporting CSS selectors.
      1
      -

    • mcp-web-tools-server

      ZephyraRR
      A
      license
      Not graded
      quality
      C
      maintenance
      A custom MCP server that provides AI agents with tools to fetch web pages, extract readable article text, extract structured data by CSS selector, and check robots.txt permissions.
      MIT

    • mcp-web-scraper

      wzx11223344
      A
      license
      Not graded
      quality
      C
      maintenance
      A comprehensive web scraping MCP server with 26 tools for fetching, parsing, extracting, and assisting with web content, returning Markdown-formatted results.
      MIT

    • MCP Website Fetcher

      electrocucaracha
      F
      license
      Not graded
      quality
      F
      maintenance
      A lightweight MCP server implementation that provides a simple tool for fetching website content, demonstrating how tools can be exposed and interacted with using the MCP protocol.
      -

    • pagewatch-mcp

      toolshedlabs-hash
      A
      license
      A
      quality
      C
      maintenance
      MCP server that provides read_page, screenshot, and pdf tools using a real browser, enabling agents to fetch clean markdown, screenshots, and PDFs from any URL.
      5
      23 npm
      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

    C2.9/5.0

    Scored across 2 tools

    Disambiguation3/5

    The two tools have broadly similar purposes - both fetch data from URLs. The distinction between 'fetch data' and 'scrape readable text content' is somewhat clear but could easily cause misselection for agents wanting raw HTML vs parsed content. The line between the two is fuzzy.

    Naming Consistency4/5

    Both tools follow the verb_noun pattern (fetch_url, scrape_url) with consistent snake_case naming. The conventions match, though the verbs are distinct in style rather than sharing a common action term.

    Tool Count2/5

    With only 2 tools, the server feels extremely thin. Even for a focused purpose like fetching web content, one might expect additional tools for handling different output formats, following redirects, or handling authentication. Two tools barely justify a server.

    Completeness2/5

    The surface appears incomplete even for the stated purpose. Missing operations like fetching HTML versus JSON versus extracted text as separate concerns, handling redirects, following links, or downloading files. The gap between 'raw fetch' and 'readable text extract' leaves a large middle ground uncovered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources