Skip to main content
Glama
libering

OmniArchive-MCP

by libering

Related Servers

Alternatives to OmniArchive-MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM agents to perform web search, scraping, and summarization outside their context window, receiving compact cited briefs via MCP while full pages are cached and viewable in a local web UI.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to mirror websites into a shared archive in the background, then browse projects, list and read text files, and run substring searches over the downloaded content. Concurrency isolation per project allows multiple sites to be mirrored in parallel with status polling over MCP.
      AGPL 3.0
    • 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
      19
      AGPL 3.0
    • 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
      A
      maintenance
      Bridges AI agents to a real browser using a persistent daemon and Chrome extension for driving actual login sessions, cookies, and tabs.
      MIT

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation3/5

    archive_url and archive_and_cite both submit a URL for archiving, so an agent must decide between them; the citation convenience in archive_and_cite is the only real differentiator and descriptions acknowledge the overlap. retry_task and get_archive_status are clearly distinct.

    Naming Consistency4/5

    All four names are verb-first snake_case (archive_url, retry_task, get_archive_status, archive_and_cite), which is predictable overall. The compound 'archive_and_cite' deviates slightly from the verb_noun pattern but remains readable.

    Tool Count4/5

    Four tools fit the narrow URL-archiving domain well: submit, check status, retry, and cite. It is a touch lean but each tool covers a distinct stage of the workflow.

    Completeness3/5

    The set covers submission, status polling, retry, and citation, but there is no way to list existing tasks, cancel a pending archive, or batch-submit URLs—notable gaps for managing multiple tasks during research.

    Maintenance

    ActivityActive
    ResponsivenessNo issues