Skip to main content
Glama
Sign In
Zearch MCP

Zearch MCP

Official
by zearchcomputer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Zearch MCP

No user-submitted related servers found.

    Related Servers

    • mcp-rag-tools

      dinamain
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible clients to retrieve relevant document chunks and fact-check generated answers against context, classifying them as fully supported, partially supported, or unsupported.
      -

    • research-workflow-studio

      BorgDiven
      A
      license
      C
      quality
      B
      maintenance
      Enables AI clients to create and read structured research records—projects, questions, specifications, implementations, executions, artifacts, evidence, evaluations, comparisons, analyses, and reports—through MCP while keeping scientific judgments and approvals human-controlled.
      37
      1
      MIT

    • rbac-rag-assistant

      Shrey-Parikh31
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to ask plain-language questions and receive answers grounded only in documents the configured role is cleared to read, with the same access-controlled tools available across any client.
      -

    • mcp-rag-platform

      mittal-umang
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables retrieval-augmented question answering with source-grounded citations, document retrieval, and idempotent ingestion through MCP tools.
      -
    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 6 tools

    Disambiguation4/5

    The six tools mostly target distinct operations: research answers questions, verify checks third-party text, get_run/list_runs retrieve history, and get_wallet/get_pricing split private balance vs. public price list. The main wrinkle is that research folds six very different modes (scrape, crawl, compare, deep, reverse) into one tool with a mode argument, so an agent must read parameters rather than pick a tool. Wallet vs. pricing is a mild adjacency but the descriptions clearly separate them.

    Naming Consistency4/5

    Four tools follow a clean verb_noun pattern (get_run, list_runs, get_wallet, get_pricing) with plural nouns on list/read endpoints. The two core tools, research and verify, are bare verbs with no object noun, which is a minor stylistic break but still readable and consistent with each other.

    Tool Count5/5

    Six tools is well-scoped for a search-and-verification service: one entry point, one checker, two history readers, two billing readers. Nothing appears redundant or missing at the count level, and the heavy mode multiplexing is handled inside research rather than by exploding the tool list.

    Completeness4/5

    The lifecycle is largely covered: submit a job, verify text, fetch a single run, list history, and inspect balance/pricing. Minor gaps remain — no cancel or delete for queued or stale runs (notable given reverse runs can take minutes and hold 10 credits), and follow-ups are only expressible via the parent_id parameter on research rather than a dedicated operation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources