Skip to main content
Glama

Related Servers

Alternatives to web-shooter

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that fetches web pages, extracts clean markdown (reducing token count), caches results, and provides searchable reading history.
      7 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that fetches web pages and extracts clean, AI-friendly Markdown content using Mozilla Readability. It provides secure web access for LLMs with built-in SSRF protection and automated content cleaning for improved context retrieval and summarization.
      1
      515 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A local, read-only MCP server that makes bookmarks from browsers, read-later apps, and export files accessible to AI assistants, enabling search, triage, and summarization without sending data anywhere.
      8
      35 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A local-first MCP server that lets AI agents read any webpage as clean Markdown, crawl whole sites within configured limits, search without API keys, and solve supported captchas locally — all without cloud services or third-party keys.
      30
      20
      AGPL 3.0

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation4/5

    crawl and links both surface URLs from a page's links, which could initially confuse an agent, but descriptions clearly separate site-wide discovery (crawl) from single-page link listing/ranking (links), and fetch is unambiguously for reading content. Boundaries are mostly clear.

    Naming Consistency4/5

    Two tools use verb-style names (crawl, fetch) while links is a noun, a minor deviation from a single convention. All are single-word, lowercase, and immediately readable, so the inconsistency is small.

    Tool Count5/5

    Three tools is exactly right for a web-reading server: discover (crawl), list/rank links (links), and read content (fetch). Each earns its place with no redundancy.

    Completeness4/5

    The core lifecycle of find-then-read is covered, including PDFs, JS-rendered pages, robots.txt compliance, and query-based relevance filtering. Minor gaps exist (no explicit sitemap or multi-URL batch crawl options), but agents can work around them by chaining crawl and fetch.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues