Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Realmint

REMOTE · MCP.REALMINT.IO · SCANNED AUG 3

Agent-native scoring, search and routing for tokenized real-world assets across multi-chain.

Available components

−34 this week 23 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.realmint.io

# add to Claude Code
claude mcp add --transport http realmint-io-mcp https://mcp.realmint.io/mcp
# ~/.codex/config.toml
[mcp_servers.realmint-io-mcp]
url = "https://mcp.realmint.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "realmint-io-mcp": {
      "type": "remote",
      "url": "https://mcp.realmint.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add realmint-io-mcp --url https://mcp.realmint.io/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  realmint-io-mcp:
    url: "https://mcp.realmint.io/mcp"
// mcp.json
{
  "mcpServers": {
    "realmint-io-mcp": {
      "type": "http",
      "url": "https://mcp.realmint.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 −38
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: 0.20 → unverified security
    • Authorization: fail → unverified security
    • Transport: pass → fail security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 31 Jul 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 56

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://mcp.realmint.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=realmint.io CN=YE2,O=Let's Encrypt,C=US 1 Jul 2026 29 Sept 2026 ECDSA 256 ECDSA-SHA384 53ab265e4b261e75a934a8684ac27e4137b
SANs: *.realmint.io, realmint.io
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of mcp.realmint.io. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
realmint.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 502
Header Value
x-frame-options SAMEORIGIN
referrer-policy same-origin
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.realmint.io/mcp HTTP error 502
http (plaintext) http://mcp.realmint.io/mcp HTTPS enforced 301 https://mcp.realmint.io/mcp
MCP tools — 16 exposed · ~2,080 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
realmint_buy ~125

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.

NameTypeReqDescription
amount_usdcnumberyes
asset_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

realmint_deposit ~48

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

realmint_get_asset ~171

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).

NameTypeReqDescription
asset_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

realmint_get_asset_history ~63

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.

NameTypeReqDescription
asset_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

realmint_get_price_history ~144

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.

NameTypeReqDescription
asset_idstringyes
daysinteger
granularitystring
NameTypeReqDescription
resultstringyes

No examples provided.

realmint_get_route_support ~90

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.

NameTypeReqDescription
asset_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

realmint_get_score ~308

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

NameTypeReqDescription
asset_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

realmint_list_assets ~53

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

realmint_list_instruments ~106

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

realmint_list_market ~111

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.

NameTypeReqDescription
idsstring
NameTypeReqDescription
resultstringyes

No examples provided.

realmint_logout ~61

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

realmint_my_wallet ~42

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

realmint_sell ~115

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.

NameTypeReqDescription
amountnumberyes
asset_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

realmint_whoami ~60

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

realmint_withdraw ~166

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.

NameTypeReqDescription
amount_usdcnumberyes
recipientstringyes
smart_account_addressstring
NameTypeReqDescription
resultstringyes

No examples provided.

realmint_x402_buy_challenge ~417

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.

NameTypeReqDescription
amount_usdcnumberyes
asset_idstring
owner_eoastringyes
NameTypeReqDescription
resultstringyes

No examples provided.