Skip to main content
Glama
jbccc

ZeroEntropy Zerank MCP Server

by jbccc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to ZeroEntropy Zerank MCP Server

No user-submitted related servers found.

    Related Servers

    • RyRank

      trigeochiral
      A
      license
      A
      quality
      C
      maintenance
      Enables reranking documents by relevance to a query through a Cohere-compatible API, so existing rerank code drops in with only a base_url change. Calls are pay-per-call in USDC via x402 or covered by a free daily tier, with no account, GPU, or model download needed.
      1
      35 PyPI
      MIT

    • genpark-contextual-compression

      alphaparkinc
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and MCP clients to compress retrieved web documents against a query, pruning irrelevant noise through deterministic algorithmic scoring so downstream context stays lean. It exposes this capability over the Model Context Protocol for integration with Claude Desktop, Cursor, and similar clients.
      8
      -

    • saar

      hpandey2023
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to retrieve relevant sections from indexed files (documents, code, etc.) via hybrid semantic/BM25 search, with citations, through the Model Context Protocol.
      Apache 2.0

    • AgentSEO MCP Server

      AgentSEO-dev
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to perform SEO searches and retrieve SEO intelligence data via the Model Context Protocol.
      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.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_reranking' has a clear and distinct purpose, so agents cannot misselect between non-existent alternatives.

    Naming Consistency5/5

    The naming pattern is trivially consistent as there is only one tool. It follows a verb_noun convention ('get_reranking'), which is clear and predictable, though no comparison with other tools is possible.

    Tool Count2/5

    A single tool is generally too few for most server purposes, as it limits functionality and suggests a thin or incomplete surface. For a 'Zerank' server, which might imply ranking or reranking operations, one tool feels insufficient to cover the domain adequately.

    Completeness2/5

    The tool set is severely incomplete for a reranking domain. With only a 'get_reranking' tool, there are obvious gaps such as creating, updating, or deleting rankings, or other related operations like listing or searching, which agents would need for full workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources