Parkour MCP
Related Servers
Alternatives to Parkour MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server that fetches web pages, extracts clean markdown (reducing token count), caches results, and provides searchable reading history.MIT
- AlicenseAqualityCmaintenanceAn 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.1114 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceAn 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-
- AlicenseAqualityBmaintenanceAn 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.58 npm1MIT
- AlicenseAqualityAmaintenanceA fast, dependency-light MCP server that converts web pages into clean Markdown, structured metadata, and classified links for language models.324 npmMIT
- AlicenseAqualityCmaintenanceAn 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.544 npm15MIT
TDQS
Scored across 13 tools
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 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.
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.
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.