Skip to main content
Glama
InfinityScrape MCP

InfinityScrape MCP

Related Servers

Alternatives to InfinityScrape MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Gives AI agents local web search and page reading with no API keys, layering a SearXNG-backed search cache with browser-based fallbacks and returning clean page text from HTML, PDF, JSON, and archived snapshots. Fetches run in Docker alongside the search engine with SSRF protection, egress filtering, and untrusted-content marking so agents can safely retrieve live web data.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to run local multi-engine web searches, fetch pages through anti-bot fallback chains, and query site-specific sources such as GitHub, npm, PyPI, Docker Hub, and Twitter/X for structured results.
      2
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to run web searches across configured providers and crawl individual pages or entire sites into deduplicated Markdown or JSON, including options for authenticated pages and CLI/API access.
      -
    • A
      license
      A
      quality
      A
      maintenance
      Provides local-first web intelligence over MCP with tools for search, fetch, crawl, extract, cache, find-similar, research, and autonomous agent loops, requiring no API keys.
      10
      2,847 npm
      5,514
      AGPL 3.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to run web searches across self-hosted SearXNG and/or You.com in parallel and to crawl single pages or whole sites into clean, deduplicated Markdown or JSON. It runs locally via STDIO or HTTP MCP transports, supports authenticated crawls, and requires no API key when using SearXNG.
      -

    TDQS

    C2.7/5.0

    Scored across 33 tools

    Disambiguation2/5

    Several clusters of tools have unclear boundaries: scrape_url vs scrape_dynamic vs scrape_batch vs deep_crawl vs search_and_scrape all fetch page content, and extract_schema vs extract_structured both do field-level extraction. The OSINT cluster (osint_domain_recon, osint_dns_audit, osint_subdomain_enumeration, osint_tech_stack, osint_ip_lookup) and osint_geoint_lookup vs osint_location_entity_search overlap heavily, forcing guesswork about which to pick.

    Naming Consistency3/5

    Most tools follow snake_case verb_noun (scrape_url, extract_pdf, search_web), but there are deviations: two tools carry a redundant '_tool' suffix (extract_reddit_thread_tool, extract_rss_feed_tool), some use a domain prefix (osint_*), and others are bare noun_verb or non-verb forms (deep_crawl, scrape_batch). Readable overall but inconsistent conventions.

    Tool Count2/5

    33 tools is well above the comfortable range for a single server and includes near-duplicate scraping and OSINT entries that could be merged. The breadth (scraping, document parsing, OSINT, RAG chunking) makes the surface feel like several servers bundled together.

    Completeness4/5

    The scraping/extraction/OSINT domain is well covered: static and dynamic scraping, crawling, sitemaps, PDF/DOCX/XLSX, images, YouTube, Reddit, RSS, and a broad OSINT suite, plus RAG chunking and diffing. Minor gaps like screenshot capture, authenticated/form-based scraping, and a generic 'get robots.txt' helper are workable around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues