Skip to main content
Glama
Sign In
agent-web-search

agent-web-search

by JerryLiu369
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to agent-web-search

No user-submitted related servers found.

    Related Servers

    • Search MCP Server

      ilgizar-valiullin
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to perform unified web searches, GitHub, and GitLab searches with caching, reranking, and fallback across multiple providers.
      4
      176 npm
      20
      MIT

    • GroundRoute

      PROJECT-B-26
      A
      license
      A
      quality
      D
      maintenance
      Web 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.
      1
      1
      MIT

    • FreeSearch MCP Server

      Ethos6
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI assistants keyless web search, news search, and full-page reading tools by querying multiple engines in parallel and returning merged results. It can run locally over stdio or remotely over HTTP for Claude, Cursor, and other agents.
      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 1 tool

    Disambiguation5/5

    With only one tool in the set, there is no possibility of confusing it with another tool. Its purpose—semantic web search for natural-language questions—is unambiguous and clearly stated.

    Naming Consistency5/5

    The single tool uses a clean snake_case verb_noun name (web_search) that is readable and conventional. No competing conventions exist to create inconsistency.

    Tool Count3/5

    A search server can legitimately be a one-tool server, so the scope is defensible. However, a single tool is thin for a search surface that could reasonably offer companion operations (e.g., page fetch/retrieval), placing it at the borderline end of the rubric.

    Completeness3/5

    Search itself is well covered, including multi-provider fallback and diagnostics, but the lifecycle dead-ends there: an agent getting only snippets has no tool to retrieve or read a specific result page. This is a notable gap an agent must work around.

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Resources