Agent Gateway (MCP)

IX RWA exposes a hosted, read-only Model Context Protocol (MCP) endpoint — the Agent Gateway. It lets AI agents and MCP-compatible clients read the protocol’s live data directly: the IX-CORE index and its constituents, protocol statistics, and wallet portfolios. It is served by the app itself, so agents connect by URL — no install, no build, no repo.

The Agent Gateway is read-only. Agent-initiated transactions (payments, allocation) are a roadmap item, gated behind the verified money-path and mainnet — see Roadmap.

Endpoint

https://testnet.ix.finance/api/mcp

Transport is Streamable HTTP with stateless JSON-RPC 2.0 (protocol version 2025-06-18; server ix-rwa 0.1.0). CORS is open, and JSON-RPC batch requests are supported. A plain GET on the endpoint returns server info and the tool names for a quick liveness check.

Tools

Tool	Arguments	Purpose
`list_assets`	`gpu?` (string), `availableOnly?` (boolean)	List index constituents with value, APY, daily revenue, and funding. Optional GPU-model filter / available-only.
`get_asset`	`id` (string, required)	Full detail for one asset, including its on-chain ownership token address.
`protocol_stats`	(none)	Protocol-level stats: AUM/NAV, NAV-per-share, total invested, protocol earnings, asset & holder counts.
`get_portfolio`	`wallet` (string, required)	A wallet’s positions, ownership, and yield.

Quickstart

List the available tools

Send an MCP tools/list request to discover the tools above and their input schemas. initialize and ping are also supported.

Call a tool

Invoke a tool with tools/call. For example, list only available H200 assets:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_assets",
    "arguments": { "gpu": "H200", "availableOnly": true }
  }
}

Read a portfolio

Note the argument is wallet (not walletAddress):

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": { "name": "get_portfolio", "arguments": { "wallet": "0x…" } }
}

Response shapes

Tool results are returned as MCP text content containing JSON. Representative fields:

list_assets

{
  "count": 3,
  "assets": [
    {
      "id": "…", "name": "…", "gpu": "H200", "numGpus": 8, "region": "…",
      "valueUsd": 250000, "apyPct": 18.4, "dailyRevenueUsd": 126.30,
      "investorPoolUsd": 150000, "fundedPct": 42.5, "fullySold": false
    }
  ]
}

protocol_stats

{
  "aumUsd": 0, "navPerShareUsd": 1.0,
  "totalInvestedUsd": 0, "totalProtocolEarningsUsd": 0,
  "assetCount": 0, "holders": 0,
  "network": "Base Sepolia (chain 84532)"
}

get_asset additionally returns description, reliabilityPct, hourlyRateUsd, tokenAddress, and the ownership split (40% IX / 60% investors). AUM and NAV-per-share come from the live on-chain vault (6-decimals), matching the app — not a database sum.

Use it from an MCP client

Add the endpoint to any MCP-compatible client (for example, Claude Code):

{
  "mcpServers": {
    "ix-rwa": { "type": "http", "url": "https://testnet.ix.finance/api/mcp" }
  }
}

Or via the CLI:

claude mcp add --transport http ix-rwa https://testnet.ix.finance/api/mcp

Data, honestly

The Gateway serves the same data the app uses. On testnet, NAV and yield are simulated in settlement but driven by live market data (the LiveDataNAVOracle, fed from live Vast.ai rates) as described in Revenue & distributions; realized on-chain figures are distinguished from simulated ones.

Get started

Protocol

Developers

Trust & Security

Resources

Agent Gateway (MCP)

Endpoint

Tools

Quickstart

Response shapes

Use it from an MCP client

Data, honestly

​Endpoint

​Tools

​Quickstart

​Response shapes

​Use it from an MCP client

​Data, honestly

Endpoint

Tools

Quickstart

Response shapes

Use it from an MCP client

Data, honestly