Realmint MCP Server

Buy `amount_usdc` of USDC worth of the RWA `asset_id` (e.g. 'paxg'). **Requires sign-in + a one-time wallet delegation** at app.realmint.io/mcp/delegate. Realmint signs server-side via your Privy delegation, capped per-trade — no key, no per-trade approval. Your smart account must already hold USDC (see realmint_deposit). Moves real funds.

Show where to send USDC to fund your buying power. **Requires sign-in.** Send USDC on Base to your EVM wallet; it funds your smart account for buys.

Get the full schema for a specific RWA by asset ID. Includes issuer details, control capabilities (freeze/mint/burn/blacklist), transferability restrictions, redemption mechanics, and legal documents. The asset ID is the lowercased ticker (e.g. "xaut", "paxg", "kau", "agri", "cgo"). Use `realmint_list_assets` to discover all available IDs — the catalog spans ~30 tokens across multiple chains and changes over time. Always read `metadata.lifecycle` from the response: a non-null lifecycle means the token is migrated/discontinued/abandoned and trading is disallowed (score is hard-capped at 49).

Get the versioned metadata change history for an asset. Each entry records what changed (created, updated) and a full schema snapshot. Useful for detecting when an issuer changes terms or control parameters.

Time-series price history for an asset. Args: asset_id: Asset identifier days: Lookback in days (1-730, default 30) granularity: Optional explicit bucket — "5m" | "1h" | "1d". Omit to auto-pick (≤2d → 5m, ≤30d → 1h, else 1d). The server cascades to coarser buckets when the requested one is empty for this asset.

List the venues and chains that can route this asset, plus per-venue backing/liquidity/social scores and policy flags. Use this to check whether a trade is even feasible before quoting — `routing_enabled=false` or an empty venue list means the asset can be inspected but not traded via Realmint.

Get the Risk & Rights Score for an asset across six dimensions: - backing (0-100): proof of reserves, audit cadence, backing mechanism - enforceability (0-100): governing law, issuer verification, legal documents - control (0-100): issuer power risk — freeze, mint, burn, blacklist, upgrade - exit (0-100): redemption, transferability, KYC/whitelist, settlement, holding periods - liquidity (0-100): market data, venue count, evidence docs - social (0-100): Twitter activity (recency-weighted; unverified handles are penalized below the worst observed tier) Also returns a weighted composite (0-100, higher is better). Weights and penalty tiers are versioned server-side — see `policy_version` in the response. Combine with the asset's `metadata.lifecycle` field (from `realmint_get_asset`) to detect dead/migrated tokens — those are score-capped at 49. Suggested thresholds for decision-making: - composite ≥ 75: typical case, proceed - 55 ≤ composite < 75: elevated friction (gates, missing audits, etc.); review the asset's flags before proceeding - composite < 55: high risk; abort or require explicit user override

List all tokenized real-world assets (RWAs) indexed by Realmint. Returns the full schema for each asset including ownership, control, transferability, redemption terms, and legal metadata.

List instruments — the real-world things tokens represent: an underlying at a specific denomination ("Silver · 1 oz") or a stock ("Apple"). Tokens sharing an instrument are interchangeable representations of the same thing. Each entry carries its member token ids, the recommended member (buyable > priced > score), and the floor price across members — use it to pick the best token for an instrument before quoting or buying.

Market snapshots for indexed RWAs: spot price, 24h change, volume, market cap, venue count, and a short price history series. Combine with `realmint_get_score` to compare risk against liquidity. Args: ids: Optional comma-separated asset IDs to filter (e.g. "xaut,paxg"). Empty = all assets. Assets without fresh market data are omitted from the response.

Sign out note: Realmint keeps no signing session — server-side signing is your standing Privy **delegation**. To fully revoke it, go to app.realmint.io/mcp/delegate. Disconnecting the connector ends this session.

Show your Realmint wallet (EVM + Solana), smart account, and balances. **Requires sign-in.** Read-only; moves no funds.

Sell `amount` of the RWA `asset_id` you hold, settling USDC back on Injective. **Requires sign-in + a one-time wallet delegation** at app.realmint.io/mcp/delegate. Realmint signs server-side via your Privy delegation — no key, no per-trade approval. Sells positions bought over MCP (held in your derived Realmint Wallet). Moves real funds.

Return the signed-in user's identity. This tool **requires authentication** — calling it triggers the Realmint sign-in (OAuth) if you're not signed in. Use it to confirm who you're acting as. Read-only; moves no funds.

Withdraw `amount_usdc` USDC from your Realmint smart account to `recipient` (any address). **Requires sign-in + a one-time wallet delegation** at app.realmint.io/mcp/delegate. Realmint signs server-side via your Privy delegation, capped per-transaction — no key, no per-withdraw approval. Native USDC on Injective. Moves real funds. `smart_account_address` (advanced/recovery, normally leave empty): sweep from a specific smart account you own that a factory rotation left behind. Only an SA CREATE2-owned by you is accepted.

Get the x402 payment requirements to fund yourself in USDC so you can buy RWAs — the agent-native on-ramp. This returns the 402 challenge only; it moves no funds. To complete funding (two signatures total, the same a human gives), the agent then, ENTIRELY CLIENT-SIDE: 1. Reads `accepts[0]` from the returned body: `payTo` is YOUR Base smart account (derived from `owner_eoa`), `maxAmountRequired` the USDC atomic amount, `asset` the Base USDC contract, `extra` the EIP-712 domain. 2. Signs an EIP-3009 `transferWithAuthorization(from=owner_eoa, to=payTo, value=maxAmountRequired, ...)` over that domain, base64-encodes the x402 PaymentPayload, and re-POSTs to `/v1/route/x402-buy` with it in the `X-PAYMENT` header. On settlement the USDC bridges custody-free to your Injective smart account. 3. Buys any RWA from that Injective balance via `POST /v1/route/intent` (signing the route as usual). The asset rests in your smart account; `send` it elsewhere if you want — exactly like a human user. Always verify `payTo` derives from your own `owner_eoa` before signing. Args: owner_eoa: Your EVM EOA — the payment signer and smart-account owner. amount_usdc: USDC to fund yourself with (human units, e.g. 25.0). asset_id: Optional RWA you intend to buy, recorded for context.