Argus
Related Servers
Alternatives to Argus
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceWeb search for AI agents across 6 engines (Serper, Brave, Exa, Tavily, Firecrawl, Perplexity) through one search tool. Routes each query to the cheapest engine that clears a quality bar and caches repeats. Hosted, streamable-HTTP, BYOK supported.11MIT
- AlicenseAqualityAmaintenanceEnables AI agents to perform reliable web searches through multiple vendors with automatic failover, keyless-first access, TTL caching, and concurrent request coalescing.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLMs and coding assistants to run web searches by concurrently aggregating multiple commercial search engines per scenario, merging and deduplicating URL-normalized results with per-call fallback. When no API keys or all commercial engines fail, it automatically degrades to key-free DuckDuckGo and Bing channels so search never goes offline.18 npmMIT
- AlicenseAqualityBmaintenanceEnables LLMs to run web searches through a single tool that fuses five providers in a tiered cascade, falling back from free sources to paid ones only when needed and returning the full routing chain. Ships with a one-click installer that detects and wirelessly configures ten AI agent CLIs.122 PyPIMIT
- AlicenseAqualityCmaintenanceFree, open-source web search gateway and MCP server for LLMs, AI agents, and RAG. It provides no-key web, code, academic, and community search with deduplication, ranking fusion, and citation-ready results.32MIT
- AlicenseAqualityFmaintenanceFree multi-source web search server for AI agents, with confidence scoring and token optimization.3118 npmApache 2.0
TDQS
Scored across 15 tools
Four tool pairs are near-duplicates distinguished only by references to a 'HTTP' vs 'HTTP-v2 evidence' authority (search_web/search_web_v2, recover_url/recover_url_v2, expand_links/expand_links_v2, extract_content/extract_content_v2), giving an agent no clear basis for choosing. Additionally, recover_url and recover_dead_article overlap, and capture_site/build_research_pack have no descriptions at all, leaving their boundaries undefined.
Names consistently follow snake_case verb_noun (search_web, expand_links, get_workflow_status, read_workflow_artifact). The only deviation is the _v2 suffix convention, which is at least applied uniformly but signals duplication rather than a distinct capability.
15 tools sits at the upper edge of a comfortable set, and roughly half of it is duplicated v1/v2 surface, so the effective unique capability count is closer to 11. The count feels inflated for the actual scope of a web-research pipeline.
The surface covers a plausible research lifecycle — search, recover, expand, extract, capture, build a research pack, and poll/read workflow output plus health and budgets. However there are no cancellation/cleanup operations for workflows or packs, and two tools (capture_site, build_research_pack) lack descriptions, making their role and coverage impossible to verify.