Skip to main content
Glama
Peteroooooooo

multi-api-web-search

by Peteroooooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to multi-api-web-search

No user-submitted related servers found.

    Related Servers

    • qsearch

      theYahia
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform web searches with full content retrieval and multi-engine provenance, including trust scoring and local corpus persistence, via MCP integration.
      1 npm
      3
      Apache 2.0

    • DeepSearch MCP

      yuemingruoan
      A
      license
      B
      quality
      C
      maintenance
      Enables web search and site-specific search capabilities through the Deepsearch model. Provides unified access to broad web retrieval and targeted site search functionality within the MCP ecosystem.
      2
      19 npm
      5
      Apache 2.0

    • Search Toolkit

      TheWiseWolfHolo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform web search, extraction, and research across multiple provider backends with persistent multi-key rotation and auditable routing. Supports MCP, CLI, and Agent Skill entry points.
      MIT

    • jupsearch-mcp

      4cya
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to run unified web searches across multiple providers such as Exa, Serper, Tavily, Firecrawl, and Jina, fusing results with reciprocal rank fusion, and to extract readable content from public web pages, PDFs, and video pages as Markdown. Provider chains are configurable, failures are isolated per provider, and responses report attempted, succeeded, failed, and skipped channels with source tracing and honest warnings.
      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

    C2.8/5.0

    Scored across 2 tools

    Disambiguation1/5

    Both tools have the exact same description and purpose, differing only in the name prefix. An agent cannot reliably choose between them because they appear to be identical duplicates.

    Naming Consistency2/5

    Both names use snake_case, but 'web_search' and 'multi_api_web_search' are near-duplicates with no clear convention. The prefixed variant is inconsistent with the generic one, making the naming feel redundant rather than patterned.

    Tool Count2/5

    Two tools exist but they appear to serve the exact same function. One tool would be appropriate for this simple search server; the extra tool is redundant and does not earn its place.

    Completeness5/5

    For a web search server, the tool surface covers the core capability of performing live internet searches. No additional operations like create, update, or delete are relevant to this domain, so there are no obvious gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources