Skip to main content
Glama

Related Servers

Alternatives to Parkour MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that fetches web pages, extracts clean markdown (reducing token count), caches results, and provides searchable reading history.
      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
      114 npm
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server for web content extraction that converts HTML pages into clean, LLM-optimized Markdown using Mozilla's Readability. It supports batch processing, intelligent multi-page crawling, and configurable caching while respecting robots.txt standards.
      25 npm
      -
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that fetches web pages and extracts clean, AI-usable context from them, enabling tools for link discovery, content search, and integrated fetch-and-search operations.
      5
      8 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to fetch web content in multiple formats (HTML, JSON, text, Markdown) with intelligent content extraction, chunk management, and browser automation support.
      5
      44 npm
      15
      MIT

    TDQS

    A4.3/5.0

    Scored across 13 tools

    Disambiguation4/5

    Each tool targets a distinct source or mode—web search, page structure, page extraction, arXiv, GitHub, Hugging Face, IETF, packages, Discourse, MediaWiki, YouTube, and comments—so misselection is unlikely. The main ambiguity is that web_fetch_incisive also auto-handles many of the same URLs as the dedicated tools, and kagi_search could overlap with domain-specific search, but the descriptions clearly steer structured lookups to the dedicated tools.

    Naming Consistency3/5

    Naming conventions are mixed: domain connectors use bare platform names like arxiv, github, ietf, and youtube, while utility tools use web_fetch_* and research_shelf, and kagi_search combines a brand with an action. The names are readable and recognizable, but there is no consistent verb_noun or action-first pattern across the set.

    Tool Count5/5

    Thirteen tools is well within the ideal range for a multi-source research and retrieval server. Each tool covers a distinct content type or workflow step, and none feels redundant or vestigial.

    Completeness4/5

    The server covers a broad research lifecycle: search, structural page inspection, targeted extraction, domain-specific retrieval for papers/code/models/RFCs/packages/forums/video, plus a research shelf for tracking and exporting sources. Minor gaps keep it from a 5: research_shelf references semantic_scholar even though no such tool exists, and the YouTube tool mentions a music sibling that is not present.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive