Skip to main content
Glama
README.md
# RyRank — MCP server

<!-- mcp-name: io.github.trigeochiral/ryrank -->

A Cohere-compatible reranker, pay-per-call in USDC on Base (x402), free tier, no signup.

Hosted API: `https://trigeochiral.com` — set it as `RYRANK_API`.

## Tool

| Tool | What |
|---|---|
| `rerank` | Rerank documents by relevance to a query. Cohere-compatible response shape (`results: [{index, relevance_score}]`), so it drops into an existing `co.rerank()` call. ~$0.001/call over x402 (roughly half Cohere Rerank's list price) or a free tier. |

## Why

A hybrid reranker, not a cross-encoder: strong when the candidates already
share vocabulary with the query, which is the common case for RAG retrieval output and
document/tool shortlists. Built for high-volume, latency- and cost-sensitive reranking —
narrowing a retrieval candidate set, deduping, triage — rather than close semantic
disambiguation between near-identical phrasings. Pay-per-call and about half the price is
the trade for that.

Verified against the real `cohere.Client`, `cohere.ClientV2` and `voyageai.Client` SDKs:
point `base_url` at this API and existing rerank code runs unmodified.

## Install

```bash
pip install ryrank-mcp
claude mcp add ryrank --env RYRANK_API=https://trigeochiral.com -- ryrank-mcp
```

or with `uvx` (no install):

```bash
claude mcp add ryrank --env RYRANK_API=https://trigeochiral.com -- uvx ryrank-mcp
```

Optional: `RYRANK_XPAYMENT` = a base64 x402 `X-PAYMENT` payload, to make paid calls past the
free tier. Without it you get 25 free calls/day per IP.

## Direct HTTP (no MCP)

```bash
curl -sX POST https://trigeochiral.com/v1/rerank -H 'content-type: application/json' \
  -d '{"query":"how do I reset my password","documents":["Go to Settings > Security and click Reset Password.","Our refund policy allows returns within 30 days."],"top_n":2}'
```

Also speaks the exact Cohere v2 (`POST /v2/rerank`) and Voyage (`POST /voyage/v1/rerank`) request
and response shapes, so their official SDKs work unmodified with just a `base_url` override — see
`https://trigeochiral.com` for details.

## License

MIT

TDQS

A4.6/5.0

Scored 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