Skip to main content
Glama
hffmnnj

openai_websearch

by hffmnnj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to openai_websearch

No user-submitted related servers found.

    Related Servers

    • OpenAI WebSearch MCP Server

      luchiniatwork
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides intelligent web search capabilities using OpenAI's Web Search API with reasoning models. Supports localized results, multiple model options, and automatic source citations for current information retrieval.
      10 npm
      -

    • websearch-mcp

      roberthamel
      A
      license
      A
      quality
      Not graded
      maintenance
      Enables web searching via SearXNG, page content extraction with Crawl4AI, and image analysis using vision language models. It provides AI agents with tools for information synthesis and web-based data retrieval through OpenAI-compatible LLM endpoints.
      3
      Apache 2.0

    • agent-web-search

      JerryLiu369
      A
      license
      A
      quality
      A
      maintenance
      Provides a unified web search tool for AI agents by running multiple search providers concurrently and returning normalized results. It integrates with Claude Code, Codex CLI, OpenCode, and Hermes.
      1
      99 PyPI
      6
      MIT

    • web-search-mcp

      Backerss
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides free web search, content fetching, image search, and deep research via SearXNG, no API keys required.
      -

    • 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
      21 npm
      3
      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.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    image_search and web_search are clearly distinct: one retrieves images, the other general web results. The names and descriptions leave no ambiguity about which tool to use for a given query.

    Naming Consistency5/5

    Both tools follow the identical <object>_search pattern, creating a predictable and consistent naming convention that aligns with their functions.

    Tool Count3/5

    With only two tools, the server feels minimal but covers the two primary search needs (general and image). It is borderline because the scope could reasonably include other search types.

    Completeness4/5

    The tool surface covers general web search and image search well, but is missing potentially common search types like news or video. Overall, the core search functionality is not left with dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources