io.github.Ryvonetwork/ryvo-protocol
NPM · @RYVONETWORK/PROTOCOL-MCP · SCANNED SEP 20
MCP server for Ryvo Protocol state reads and prepare-only payment-channel actions.
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 Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects toml 3.0.0, reached via @coral-xyz/anchor > toml. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 23 of 67 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
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 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 532 tokens (~53/item across 10 items; 9 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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 io.github.Ryvonetwork/ryvo-protocol MCP server?
io.github.Ryvonetwork/ryvo-protocol runs locally as an npm package, launched with npx -y @ryvonetwork/protocol-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @ryvonetwork/protocol-mcp
claude mcp add ryvonetwork-ryvo-protocol -- npx -y @ryvonetwork/protocol-mcp
{
"mcpServers": {
"ryvonetwork-ryvo-protocol": {
"command": "npx",
"args": [
"-y",
"@ryvonetwork/protocol-mcp"
]
}
}
} {
"servers": {
"ryvonetwork-ryvo-protocol": {
"command": "npx",
"args": [
"-y",
"@ryvonetwork/protocol-mcp"
]
}
}
} codex mcp add ryvonetwork-ryvo-protocol -- npx -y @ryvonetwork/protocol-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ryvonetwork-ryvo-protocol": {
"type": "local",
"command": [
"npx",
"-y",
"@ryvonetwork/protocol-mcp"
],
"enabled": true
}
}
} openclaw mcp add ryvonetwork-ryvo-protocol --command npx --arg -y --arg @ryvonetwork/protocol-mcp
mcp_servers:
ryvonetwork-ryvo-protocol:
command: "npx"
args: ["-y", "@ryvonetwork/protocol-mcp"] {
"McpServers": {
"ryvonetwork-ryvo-protocol": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@ryvonetwork/protocol-mcp"
]
}
}
} assistant mcp add ryvonetwork-ryvo-protocol -t stdio -c npx -a -y @ryvonetwork/protocol-mcp
{
"mcpServers": {
"ryvonetwork-ryvo-protocol": {
"command": "npx",
"args": [
"-y",
"@ryvonetwork/protocol-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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −2
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −2
- Stability: pass → 0.83 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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 npm/@ryvonetwork/protocol-mcp@0.5.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 4 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-528h-pc64-c93x | CVE-2026-71429 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-82x6-q7mm-w9cf | CVE-2026-77465 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-v5mp-jgw5-2x6j | CVE-2026-63376 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L | yes |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 67 packages
| Packages resolved | 67 |
|---|---|
| Deprecated | 2 |
| Stale | 19 |
| No linked repository | 3 |
| 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 →
ryvo_protocol_channel ~61
Fetch a channel by payer/payee participant IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| payeeId | integer | yes | – |
| payerId | integer | yes | – |
| programId | string | – | – |
| rpcUrl | string | – | – |
| tokenId | integer | – | – |
No output schema declared.
No examples provided.
ryvo_protocol_clearing_preview ~92
Preview BLS clearing-round message size and settlement-event compression for a candidate participant/channel count.
| Name | Type | Req | Description |
|---|---|---|---|
| bytesLimit | integer | – | – |
| channels | integer | yes | – |
| cluster | string | – | – |
| mint | string | – | – |
| participants | integer | yes | – |
| programId | string | – | – |
| targetCumulative | string | – | – |
| tokenId | integer | – | – |
No output schema declared.
No examples provided.
ryvo_protocol_config ~36
Fetch Ryvo Protocol global config and token registry.
| Name | Type | Req | Description |
|---|---|---|---|
| programId | string | – | – |
| rpcUrl | string | – | – |
No output schema declared.
No examples provided.
ryvo_protocol_headroom ~71
Compute gateway spendable headroom for a channel.
| Name | Type | Req | Description |
|---|---|---|---|
| latestAcceptedCommitted | string | yes | – |
| payeeId | integer | yes | – |
| payerId | integer | yes | – |
| programId | string | – | – |
| rpcUrl | string | – | – |
| tokenId | integer | – | – |
No output schema declared.
No examples provided.
ryvo_protocol_participant ~43
Fetch a participant account by owner public key.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | – |
| programId | string | – | – |
| rpcUrl | string | – | – |
No output schema declared.
No examples provided.
ryvo_protocol_prepare_action ~35
Return a concrete prepare-only instruction/account/message plan for any supported Ryvo Protocol action.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
No output schema declared.
No examples provided.
ryvo_protocol_prepare_gateway_commitment ~89
Prepare a gateway cumulative commitment payload and message bytes. Does not sign.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster | string | – | – |
| committedAmount | string | yes | – |
| payeeId | integer | yes | – |
| payerId | integer | yes | – |
| programId | string | – | – |
| signature | string | – | – |
| signer | string | yes | – |
| tokenId | integer | – | – |
No output schema declared.
No examples provided.
ryvo_protocol_token ~59
Resolve the canonical devnet USDC token metadata from env, registry, or deployment config.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | – | – |
| programId | string | – | – |
| rpcUrl | string | – | – |
| tokenId | integer | – | – |
No output schema declared.
No examples provided.
ryvo_protocol_verify_gateway_commitment ~28
Verify a signed gateway cumulative commitment envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.Ryvonetwork/ryvo-protocol MCP server?
io.github.Ryvonetwork/ryvo-protocol is an MCP server listed in the public MCP registry as io.github.Ryvonetwork/ryvo-protocol. MCP server for Ryvo Protocol state reads and prepare-only payment-channel actions. This page covers its npm package (@ryvonetwork/protocol-mcp).
Is the io.github.Ryvonetwork/ryvo-protocol MCP server safe to use?
io.github.Ryvonetwork/ryvo-protocol scores 76 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.Ryvonetwork/ryvo-protocol MCP server expose?
io.github.Ryvonetwork/ryvo-protocol exposes 9 tools: ryvo_protocol_config, ryvo_protocol_token, ryvo_protocol_participant, ryvo_protocol_channel, ryvo_protocol_headroom, and 4 more. Their descriptions and schemas cost roughly 514 tokens of context every time the server is loaded.
Is the io.github.Ryvonetwork/ryvo-protocol MCP server still maintained?
io.github.Ryvonetwork/ryvo-protocol 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 io.github.Ryvonetwork/ryvo-protocol MCP server under?
io.github.Ryvonetwork/ryvo-protocol declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.