Ryvo Gateway
Connect your agent to Ryvo Gateway for x402-paid API calls, Helius wallet flows, and token market data while prototyping web3 or paid-API products.
Overview
Ryvo Gateway MCP is an MCP server for the Build phase that integrates x402 payments, Helius Wallet, and token market data via Ryvo Gateway.
What is this MCP server?
- Ryvo Gateway MCP for x402 auth, Helius Wallet, and Tokens API market data
- npm package @ryvonetwork/gateway-mcp with stdio transport
- RYVO_SIGNER_COMMAND hook runs after HTTP 402 with auth JSON on stdin
- Configurable gateway base URL, wallet profile, and RYVO_PAYMENT_MAX_AMOUNT_USD guardrails
- Server version 0.4.2
- Default gateway base URL https://gateway.ryvo.network
- Stdio transport via npm identifier @ryvonetwork/gateway-mcp
What problem does it solve?
Agent-built apps that hit x402-protected APIs need custom 402 handling, signing, and wallet wiring that slows integration work.
Who is it for?
Advanced solo builders shipping crypto-native or x402-paid API features who already use Ryvo Gateway and Helius wallet tooling.
Skip if: Founders who only need conventional card checkout, or anyone unwilling to operate a custom signer command securely.
What do I get? / Deliverables
After npm stdio setup and signer configuration, your agent can prepare auth, complete paid gateway calls, and query token market data through MCP tools.
- MCP-callable Ryvo Gateway requests with x402 auth preparation
- Wallet- and token-market data access wired into agent-driven build workflows
Recommended MCP Servers
Journey fit
Build → Integrations is the shelf because the server is a protocol bridge (x402, wallet, tokens API), not a launch or growth playbook. Integrations fits wiring payment-aware HTTP, signer hooks, and market data into the app or agent you are actively constructing.
How it compares
Web3 and x402 gateway MCP integration, not a generic REST skill or a hosted wallet UI.
Common Questions / FAQ
Who is Ryvo Gateway MCP for?
It is for developers and agent operators integrating Ryvo Gateway x402 flows, Helius Wallet, and token APIs from Claude Code, Cursor, or other MCP hosts.
When should I use Ryvo Gateway MCP?
Use it during Build integrations while you prototype paid API access, wallet auth, and market data features against gateway.ryvo.network.
How do I add Ryvo Gateway MCP to my agent?
Install @ryvonetwork/gateway-mcp via npm, configure stdio in your MCP client, set optional RYVO_GATEWAY_BASE_URL and payment caps, and define RYVO_SIGNER_COMMAND for post-402 signing.