RyRank
Related Servers
Alternatives to RyRank
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA generic Model Context Protocol (MCP) server for high-accuracy document reranking using sentence-transformers (Cross-Encoder). Ideal for enhancing RAG and AI agent decision-making. sentence-transformers (Cross-Encoder) を使用して文書の関連度を再計算・ソートする汎用 MCP (Model Context Protocol) サーバー。11Apache 2.0
- AlicenseNot gradedqualityAmaintenanceCrypto-native LLM gateway with OpenAI-compatible API and per-token USDC payments on Solana via the x402 protocol.10,440 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to compress retrieved web documents against a query, pruning irrelevant noise so only the most relevant context reaches the model. It runs as a zero-dependency Python MCP server that accepts a query payload and returns structured, scored output.7-
- AlicenseNot gradedqualityBmaintenanceEnables agents to optimize context-window attention by reordering retrieved documents so critical evidence lands at prompt boundaries, mitigating lost-in-the-middle degradation. It combines BM25 lexical scoring, dense vector similarity, reciprocal rank fusion, knowledge-graph expansion, and recency-decay memory caching, exposed as a zero-dependency MCP stdio server.7MIT
- AlicenseAqualityCmaintenancePay-per-use clean web reader for AI agents. URL in, markdown plus metadata out, in milliseconds. Settled per-call in USDC over x402 — no signup, no API keys.1102 npm3MIT

Agent Search Proofficial
FlicenseNot gradedqualityAmaintenanceEnables agent-native web search and multi-angle research synthesis with pay-per-call USDC payments on Base via x402, requiring no API keys or subscriptions.-
TDQS
Scored across 1 tool
With a single tool, there is no possibility of misselection; the one operation 'rerank' is unambiguous and its scope (per-call document reordering for a query) is clearly stated in the description.
A single lowercase, snake_case-style verb name 'rerank' establishes no conflicting convention and matches the standard terminology of the reranking domain.
The server is deliberately a one-endpoint reranking service, so one tool is defensible and well-scoped rather than bloated; however, a lone tool is on the thin side compared with typical multi-tool surfaces, leaving little room for related operations.
For a rerank-as-a-service API the core operation is fully covered, including the response shape and document limits. Minor gaps exist around auxiliary operations (e.g. model/version selection, usage or quota introspection), but none block the primary workflow.