Ryvo Gateway

io.github.RyvonetworkPublished by GitHub account Ryvonetworkv0.4.2Updated Oct 25, 2026

MCP server for Ryvo Gateway x402, Helius Wallet, and Tokens API market data.

VerifiedSTDIODesktop onlyDatabasesFinance

Overview

AI-generated overview

A local MCP server that connects an assistant to the Ryvo Gateway for x402 payments, Helius wallet data and token market data.

What you can do
Provides gateway access for x402 payment flows, including preparing an auth request and running an auth call after an HTTP 402 response through a configured signer command. Exposes Helius wallet data and Tokens API market data through the gateway. Applies optional spend controls, a per-request maximum and a daily authorized limit, to payment requests. Uses a wallet profile hint passed to signer hooks.
When to use it
Use it when an assistant needs to query Ryvo Gateway market or wallet data, or to handle x402 payment challenges through a local signer. It suits setups where spending limits and a signer command can be configured deliberately.
Requirements
Runs locally over stdio from the npm package @ryvonetwork/gateway-mcp, so Node.js is needed. Optional environment variables: RYVO_GATEWAY_BASE_URL (defaults to the hosted gateway), RYVO_PAYMENT_DAILY_LIMIT_USD, RYVO_PAYMENT_MAX_AMOUNT_USD, RYVO_SIGNER_COMMAND and RYVO_WALLET_PROFILE. Network access to the gateway is required.
Before you install
The server can trigger payments: RYVO_SIGNER_COMMAND is spawned after an HTTP 402 and receives auth-request JSON on stdin, so it can sign and spend. Set RYVO_PAYMENT_MAX_AMOUNT_USD and RYVO_PAYMENT_DAILY_LIMIT_USD before use. Wallet-related data and requests go to the configured gateway base URL, so point RYVO_GATEWAY_BASE_URL only at a trusted endpoint.

Installation

In SourceWeft

  1. Open Ryvo Gateway in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.