Skip to main content
Glama
liujp2015

multsearch-mcp

by liujp2015
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to multsearch-mcp

No user-submitted related servers found.

    Related Servers

    • google-search-mcp-v2

      ye4wzp
      A
      license
      B
      quality
      C
      maintenance
      MCP server for Claude Code that provides Google text search, web content extraction, and image search with dual-platform (Google Images + Pinterest) and AI visual analysis with quality scoring.
      5
      MIT

    • Prism

      frederikb96
      A
      license
      Not graded
      quality
      C
      maintenance
      Multi-level web search MCP server that wraps Claude, Gemini, Perplexity, and Tavily behind a unified interface, enabling multi-depth searches with session management and provider selection.
      MIT

    • Perplexity MCP Server

      RossH121
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables Claude to perform web searches using Perplexity's API with intelligent model selection based on query intent and support for domain and recency filtering.
      6
      4
      MIT

    • codex-web-search-mcp

      dhicoc
      A
      license
      A
      quality
      A
      maintenance
      Zero-dependency MCP server that wraps OpenAI Codex's standalone search endpoint into codex_web_search and codex_web_research tools for Claude Code, enabling real-time web search and multi-step deep research independent of the underlying model.
      2
      34 npm
      2
      MIT

    • web-fetch-mcp

      bpzx
      A
      license
      A
      quality
      C
      maintenance
      MCP server for web page fetching (converting to Markdown/text with automatic fallback between Tavily and Firecrawl) and web search via Tavily.
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a distinct purpose: configuration, search (two providers), source retrieval, URL fetch, site mapping, and model switching. The two search tools (web_search and gemini_search) overlap in function but descriptions clearly position gemini_search as a cross-validation path, so an agent can disambiguate. Overall boundaries are clear.

    Naming Consistency3/5

    Naming mixes verb-first and object-first conventions: get_config_info/get_sources/switch_model are verb_noun, while web_search/web_fetch/web_map/gemini_search are object_verb (or proper-noun_verb). This inconsistency is noticeable but all names are readable and lower_snake_case, so it is not chaotic.

    Tool Count5/5

    Seven tools is well within the ideal 3–15 range. Each tool covers a distinct capability (config, search, sources, fetch, map, model switch) and none seem redundant or filler.

    Completeness5/5

    The surface covers the full workflow: search via two providers, retrieve sources via session_id, fetch single URLs, map website structures, and manage configuration/model. There are no obvious dead ends; the only minor gap might be a way to clear cache, but that is not essential to the core search/fetch/map domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources