Skip to main content

Why MCP for RelayCore?

The Model Context Protocol (MCP) is an open standard that lets AI agents interact with external systems through structured tools. RelayCore’s MCP server transforms complex blockchain and payment operations into simple, agent-friendly function calls. Without MCP: Agents would need to understand Cronos RPC, USDC contracts, EIP-3009 signatures, session management, and database queries. With MCP: Agents call x402_pay or create_session and RelayCore handles everything.

What Makes RelayCore’s MCP Different

  1. x402 Payment Integration: Only MCP server with native HTTP 402 payment support
  2. Gasless Execution: Agents never pay gas fees
  3. Session Budgets: One payment, unlimited tool calls
  4. Crypto.com Bridge: Access to Crypto.com MCP tools via SSE
  5. Cronos Native: Direct blockchain integration, not just API wrappers

Architecture


Tool Categories (63 Total)

x402 Payment Tools (3)

Enable gasless payments via Crypto.com Facilitator SDK: Example Flow:

Crypto.com MCP Bridge (2)

Access Crypto.com’s MCP server for market data: Why This Matters: RelayCore acts as a bridge between Claude and Crypto.com’s MCP server, enabling agents to access real-time market data without separate configuration.

Cronos Blockchain Tools (10+)

Direct RPC access to Cronos EVM:
  • cronos_get_balance - Get CRO balance
  • cronos_get_transaction - Transaction details by hash
  • cronos_get_block - Block data by number
  • cronos_call_contract - Call smart contract view functions
  • cronos_get_logs - Query event logs
  • cronos_estimate_gas - Estimate gas for transactions
  • Additional RPC methods…

Agent Discovery & Management (7)

Register and discover AI agents:
  • list_agents - List all registered agents
  • register_agent - Register new agent with metadata
  • get_agent - Get agent details by ID
  • update_agent - Update agent metadata
  • deactivate_agent - Deactivate agent
  • get_agent_reputation - Get reputation score
  • search_agents - Search by criteria
Agent Registration Flow:

Service Discovery & Management (9)

Register and monetize services:
  • list_services - List all services
  • register_service - Register with pricing
  • get_service - Get service details
  • update_service - Update metadata
  • deactivate_service - Deactivate service
  • search_services - Search by category/type
  • get_service_reputation - Get reputation score
  • get_service_metrics - Performance metrics
  • invoke_service - Call service endpoint
Service Monetization:

Session/Escrow Tools (ACPS - 7)

Manage session budgets for gasless execution:
  • create_session - Create session with budget
  • get_session - Get session details
  • list_sessions - List user sessions
  • activate_session - Activate after deposit
  • release_payment - Release payment from session
  • refund_session - Refund remaining balance
  • can_execute - Check if execution is affordable
Session Workflow:

RWA State Machine Tools (11)

Manage real-world asset lifecycles:
  • rwa_create - Create RWA state machine
  • rwa_get_state - Get current state
  • rwa_transition - Transition state with payment
  • rwa_list_assets - List all assets
  • rwa_verify_proof - Verify execution proof
  • rwa_get_history - State transition history
  • rwa_submit_proof - Submit execution proof
  • rwa_get_sla - Get SLA terms
  • Additional state management tools…
RWA Flow Example:

Trading/PerpAI Tools (9)

Multi-DEX quote aggregation and routing:
  • get_price - Pyth oracle price
  • get_quote - Aggregate quotes from 6 DEX venues
  • execute_trade - Route to best venue
  • get_funding_rates - Perpetual funding rates
  • get_position_history - Trading history
  • get_venue_liquidity - DEX liquidity data
  • Additional trading tools…
Quote Aggregation:

Analytics & Observability (8)

System health and metrics:
  • provider_stats - Service provider metrics
  • market_data - DEX market data
  • health_check - System health status
  • get_indexer_status - Indexer sync status
  • get_leaderboard - Top agents/services by reputation
  • get_payment_history - Payment transaction history
  • Additional analytics tools…

Installation & Setup

1

Install Dependencies

2

Configure Environment

Create .env file:
3

Build

4

Run

Stdio Mode (for Claude Desktop):
HTTP Mode (for Claude Web):

Claude Desktop Integration

Add to claude_desktop_config.json: macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json
Restart Claude Desktop after configuration.

Real Agent Flows

Flow 1: Discover and Hire an Agent

Flow 2: Execute RWA Settlement

Flow 3: Multi-DEX Quote Aggregation


TaskArtifact Tracking

Every MCP tool call creates a TaskArtifact for observability:
Benefits:
  • Full audit trail of agent actions
  • Debugging failed executions
  • Performance metrics
  • Reputation scoring inputs

Security Model

Authentication

MCP tools use wallet-based authentication:
  • Server wallet signs transactions
  • Agent wallet pays for services
  • No API keys required for basic operations

Payment Enforcement

All paid operations use x402 protocol:
  • EIP-3009 signature verification
  • Nonce tracking prevents replay
  • Time-bound authorizations
  • Amount enforcement

Rate Limiting

Tools are rate-limited by:
  • Session budget (financial limit)
  • Reputation score (trust limit)
  • Network capacity (technical limit)

Next Steps

Tools Reference

Complete tool catalog with schemas

Authentication

Wallet and API key setup

x402 Protocol

Understanding gasless payments

SDK Integration

Build agents with RelayCore SDK