Schema | RyRank

RyRank

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`RYRANK_API`	Yes	Hosted RyRank API URL, e.g. https://trigeochiral.com. Set it as RYRANK_API.
`RYRANK_XPAYMENT`	No	Optional base64 x402 X-PAYMENT payload, to make paid calls past the free tier. Without it you get 25 free calls/day per IP.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Tools

Functions exposed to the LLM to take actions

Name Description

Name	Description
rerankA	Rerank a list of documents/passages by relevance to a query. Cohere-compatible response (`results: [{index, relevance_score}]`), so it drops into an existing rerank call. One pass, no GPU, no model download, NO ACCOUNT - $0.001 USDC per call over x402 (about half of Cohere Rerank) or a free tier. Documents are supplied per call and discarded - this is NOT a persistent index. Best when the candidates already share vocabulary with the query (typical RAG retrieval output); it favours shared wording over deep pairwise scoring. Up to 1000 docs per call.

rerankA

Rerank a list of documents/passages by relevance to a query. Cohere-compatible response (results: [{index, relevance_score}]), so it drops into an existing rerank call. One pass, no GPU, no model download, NO ACCOUNT - $0.001 USDC per call over x402 (about half of Cohere Rerank) or a free tier. Documents are supplied per call and discarded - this is NOT a persistent index. Best when the candidates already share vocabulary with the query (typical RAG retrieval output); it favours shared wording over deep pairwise scoring. Up to 1000 docs per call.

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
No resources

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.6/5.0

Scored 2026-10-04 15:30 across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

A single lowercase, snake_case-style verb name 'rerank' establishes no conflicting convention and matches the standard terminology of the reranking domain.

Tool Count4/5

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.

Completeness4/5

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.

Maintenance

ActivitySlowing

ResponsivenessNo issues

Resources

Need Help?

Related Servers