Lyrenth
OfficialRelated Servers
Alternatives to Lyrenth
- AlicenseAqualityAmaintenanceThis server enables LLMs to retrieve and process content from web pages, converting HTML to markdown for easier consumption.41181,183 PyPI91,276MIT
- AlicenseAqualityBmaintenanceA Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.819,044 npm5,134MIT
- AlicenseBqualityCmaintenanceExposes the Exa web search API as an MCP server, providing tools for web searching, content retrieval, and similar page discovery. It also supports advanced features like AI-generated answers and automated research task management.9MIT
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to read web pages reliably, returning clean markdown content, hyperlinks, and metadata without navigation or ad noise.36 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to fetch any public web page as clean Markdown, retrieve page metadata (title, description, canonical URL, OpenGraph/Twitter cards, JSON-LD), and crawl a page plus up to four linked same-site pages. Calls are paid per use in USDC via x402/MPP with no API key or account, and invalid inputs or unfetchable pages are never charged.3MIT
- AlicenseAqualityBmaintenanceEnables AI agents to read clean Markdown from any URL and assess source quality with AI-readability scores.640 npm1MIT
- AlicenseAqualityBmaintenanceGive your AI the ability to read the web. Fetches URLs as clean markdown with 9 fallback strategies.257 npm9MIT
- AlicenseAqualityBmaintenanceEnables reading web pages and PDFs as clean Markdown, extracting main content and letting agents query for relevant passages, outline sections, search in-page, and list links while respecting robots.txt and blocking private addresses.4MIT
- AlicenseNot gradedqualityDmaintenanceConverts URLs into clean, LLM-ready markdown, respecting robots.txt and never bypassing anti-bot measures or paywalls.MIT
TDQS
Scored across 3 tools
read_url and read_urls are clearly distinguished as single-page versus batch reading, while check_usage serves a completely separate purpose. There is no meaningful overlap or ambiguity between any of the tools.
All tool names follow a consistent verb_noun snake_case pattern: read_url, read_urls, and check_usage. The pluralization of read_urls naturally signals the batch variant without breaking the naming convention.
Three tools is well-scoped for a focused web-reading server: single read, batch read, and usage checking each earn their place. The small surface area matches the narrow, clear purpose.
The tool set fully covers the apparent domain: reading a single page, reading multiple pages at once, and checking account usage. There are no obvious missing operations or dead ends for the stated purpose.