Skip to main content
Glama
Sign In
AllSearch MCP

AllSearch MCP

by Windrunner20
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to AllSearch MCP

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.
      8 npm
      4
      Apache 2.0

    • MCP Info Gatherer

      ESkuratov
      F
      license
      A
      quality
      D
      maintenance
      Enables searching and gathering information from multiple online sources (web, Twitter/X, Telegram, GitHub, Hugging Face, arXiv) through a unified MCP interface.
      12
      -

    • grok-build-plugin

      VasiHemanth
      A
      license
      Not graded
      quality
      C
      maintenance
      Live X (Twitter) and web search for any coding agent through your existing Grok subscription. Exposes a grok_search MCP tool, so no X API key or X developer account is needed.
      63 npm
      29
      Apache 2.0

    • MyWebSearch MCP

      iuiu-py
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to perform unified web research through a single MCP server, including search, page fetching, recursive crawling, document parsing, YouTube transcript extraction, and deep multi-query research.
      3
      -
    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/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: search runs a new web query, fetch reads a known URL, read_result pages through previously stored results without calling providers, and health reports provider/cache state. The boundary between search and fetch is explicit (query vs. known URL), so an agent can select without confusion.

    Naming Consistency4/5

    Names are all lowercase snake_case and readable, with three simple single-word tools (search, fetch, health) and one verb_noun compound (read_result). This is mostly consistent, but the lack of a uniform verb_noun pattern keeps it from a perfect score.

    Tool Count5/5

    Four tools is a well-scoped set for a web search/fetch server: search, fetch, paged result reading, and diagnostics each cover a necessary part of the workflow without redundancy. No tool feels extraneous or missing in count.

    Completeness5/5

    For a read-only retrieval domain, the lifecycle is covered: search creates result ids, read_result pages stored results without providers, fetch reads known URLs including special forum APIs, and health exposes configuration and probe diagnostics. No obvious operational gap remains for agent use.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources