mcpField
R
ryvo-gateway

ryvo-gateway

Local
github.com/RyvonetworkFinance

About ryvo-gateway

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

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"ryvonetwork-ryvo-gateway": {
"command": "npx",
"args": [
"-y",
"@ryvonetwork/gateway-mcp"
],
"env": {
"RYVO_GATEWAY_BASE_URL": "<RYVO_GATEWAY_BASE_URL>",
"RYVO_SIGNER_COMMAND": "<RYVO_SIGNER_COMMAND>",
"RYVO_WALLET_PROFILE": "<RYVO_WALLET_PROFILE>",
"RYVO_PAYMENT_MAX_AMOUNT_USD": "<RYVO_PAYMENT_MAX_AMOUNT_USD>",
"RYVO_PAYMENT_DAILY_LIMIT_USD": "<RYVO_PAYMENT_DAILY_LIMIT_USD>"
}
}
}
}
Run commandnpx -y @ryvonetwork/gateway-mcp
Environment variables to set
RYVO_GATEWAY_BASE_URLOptional Ryvo Gateway base URL. Defaults to https://gateway.ryvo.network.
RYVO_SIGNER_COMMANDExecuted only by ryvo_gateway_auth_call after an HTTP 402: spawns once with the normalized auth-request JSON on stdin (same shape as ryvo_gateway_prepare_auth). Stdout must be JSON auth output (headers map, or SIWX address+signature). On Windows, npx/npm run under cmd.exe; treat RYVO_SIGNER_COMMAND as untrusted if an attacker controls it.
RYVO_WALLET_PROFILEOptional Ryvo wallet profile hint passed to signer hooks.
RYVO_PAYMENT_MAX_AMOUNT_USDOptional x402 maximum USD amount per request.
RYVO_PAYMENT_DAILY_LIMIT_USDOptional x402 daily authorized spend limit in USD.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@ryvonetwork/gateway-mcp0.4.2

Tools

15

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
baseUrlstringNoGateway base URL. Defaults to RYVO_GATEWAY_BASE_URL or production.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.