RyRank
PYPI · RYRANK-MCP · SCANNED SEP 20
Cohere-compatible pay-per-call reranker, no signup, x402/USDC
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 9 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 202 tokens (~202/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the RyRank MCP server?
RyRank runs locally as a PyPI package, launched with uvx ryrank-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · ryrank-mcp
claude mcp add trigeochiral-ryrank -- uvx ryrank-mcp
{
"mcpServers": {
"trigeochiral-ryrank": {
"command": "uvx",
"args": [
"ryrank-mcp"
]
}
}
} {
"servers": {
"trigeochiral-ryrank": {
"command": "uvx",
"args": [
"ryrank-mcp"
]
}
}
} codex mcp add trigeochiral-ryrank -- uvx ryrank-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"trigeochiral-ryrank": {
"type": "local",
"command": [
"uvx",
"ryrank-mcp"
],
"enabled": true
}
}
} openclaw mcp add trigeochiral-ryrank --command uvx --arg ryrank-mcp
mcp_servers:
trigeochiral-ryrank:
command: "uvx"
args: ["ryrank-mcp"] {
"McpServers": {
"trigeochiral-ryrank": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"ryrank-mcp"
]
}
}
} assistant mcp add trigeochiral-ryrank -t stdio -c uvx -a ryrank-mcp
{
"mcpServers": {
"trigeochiral-ryrank": {
"command": "uvx",
"args": [
"ryrank-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +19
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.27 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/ryrank-mcp@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 9 packages
| Packages resolved | 9 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
rerank RyRank — rerank documents by a query ~202
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 is a lexical-semantic method, not a cross-encoder. Up to 1000 docs per call.
| Name | Type | Req | Description |
|---|---|---|---|
| documents | array | yes | 2-1000 documents (strings) |
| query | string | yes | the query to rank against |
| return_documents | boolean | – | include the document text in each result |
| top_n | integer | – | return only the top N (default: all) |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | – | – |
| results | array | yes | – |
No examples provided.
What is the RyRank MCP server?
RyRank is an MCP server listed in the public MCP registry as io.github.trigeochiral/ryrank. Cohere-compatible pay-per-call reranker, no signup, x402/USDC. This page covers its PyPI package (ryrank-mcp).
Is the RyRank MCP server safe to use?
RyRank scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RyRank MCP server expose?
RyRank exposes 1 tool: rerank. Their descriptions and schemas cost roughly 202 tokens of context every time the server is loaded.
Is the RyRank MCP server still maintained?
RyRank is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the RyRank MCP server under?
RyRank declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.