AgentSearch MCP
Related Servers
Alternatives to AgentSearch MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceSelf-hosted web search and page extraction for AI agents. Stdio MCP server, HTTP API and Python/npm CLI.862 npm39 PyPI2MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to search the web and fetch individual pages through two stdio tools, returning ranked results or extracted page content, titles and outbound links. It wraps a hosted, API-key-authenticated service (or a local daemon) with zero runtime dependencies.13 npmMIT
- AlicenseAqualityBmaintenanceEnables MCP clients to search the live web and fetch any URL as clean text through Ollama's web search and fetch APIs, returning ranked results with page text and outgoing links. Runs as a single dependency-free stdio server, so agents can ground their answers with current web content without a separate search vendor.29 npmMIT
- FlicenseNot gradedqualityDmaintenanceRemote MCP connector for AgentSearch API that exposes web search, instant answers, and URL-to-clean-text fetching as typed MCP tools for agents and RAG pipelines.-
- AlicenseAqualityCmaintenanceExposes DeepSeek's Search and Fetch REST APIs as two read-only MCP tools, letting any MCP-capable agent run ranked web searches and retrieve individual pages as truncated Markdown. Works with whichever model the host runs, over stdio or Streamable HTTP.2MIT
- AlicenseAqualityAmaintenanceEnables AI agents to run web and image searches across nine engines with automatic fallback and ad filtering, fetch pages and PDFs as Markdown, and search WeChat Official Account articles — all without requiring a search account or API key out of the box. Works over stdio or Streamable HTTP with any MCP-capable client.5803 npmApache 2.0
TDQS
Scored across 5 tools
The five tools have clearly distinct roles, and each description explicitly cross-references the others to guide selection. The only mild overlap is between extract and render, which both fetch page content, but their static-vs-JavaScript distinction is well explained.
All names share the agentsearch_ prefix and use snake_case, making the set predictable. However, the patterns are not perfectly uniform: web_search, review_lookup, and review_submit use noun_action, while extract and render are bare verbs with implied objects.
Five tools are well-scoped for a focused search, extraction, rendering, and review-board service. Each tool has a clear place, with no redundant or filler operations.
The surface covers the core lifecycle: finding pages, fetching static pages, rendering JavaScript-heavy pages, and both looking up and submitting service reviews. There are no obvious dead ends for the stated purpose.