Alka Search MCP
Related Servers
Alternatives to Alka Search MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and LLM apps to run live web searches and fetch public web pages as Markdown, returning structured search results and page content through MCP clients.1Apache 2.0
- AlicenseAqualityCmaintenanceEnables any MCP client to run keyless multi-engine web searches with RRF fusion, fetch pages and documents as Markdown, and full-text search a local SQLite index. It keeps queries and cached content on the user's machine, degrading gracefully across engine tiers when providers are blocked or rate-limited.8MIT
- AlicenseAqualityCmaintenanceEnables MCP-compatible clients to search the web and fetch HTTP/HTTPS pages as Markdown, returning result metadata such as titles, URLs, dates, relevance, and summaries.252 npm1MIT
- AlicenseAqualityDmaintenanceEnables AI agents to perform multi-engine web search, fetch web pages, and extract clean Markdown content via MCP, with no API keys required.377 PyPI8MIT
- AlicenseAqualityBmaintenanceGives any MCP client keyless web, news, semantic, and GitHub search plus a token-efficient reader-mode page and text-PDF fetcher, with engine fallback and a local sqlite cache. It enables agents to keep researching the web without API keys, signups, or account quotas.51MIT
- AlicenseAqualityCmaintenanceEnables keyless multi-engine web, news, image, and video metasearch plus full-page markdown extraction for AI agents over MCP, with resilient fallback across DuckDuckGo, Bing, Brave, Google, and other backends.6MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: web_search finds pages, fetch_page reads a URL, and fetch_llms_txt retrieves a domain's llms.txt. The descriptions explicitly state ordering and when to use one over the other, leaving no real overlap.
All three names use consistent snake_case with an action-oriented verb or clear resource label (web_search, fetch_page, fetch_llms_txt). The pattern is predictable and readable throughout.
Three tools are well-scoped for a free search-and-fetch server; each earns its place and there is no redundancy. The count matches the narrow purpose without bloat or thinness.
The core lifecycle (search, fetch page, fetch llms.txt) is covered cleanly with no dead ends. Minor gaps exist, such as no pagination or result-filtering for deeper searches, but agents can work around them.