Finance · Remote MCP server
Rubin Exchange
Rubin: self-custody DEX for crypto perpetuals & spot - trade, read positions, orders, balances.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
trade.rubin/exchange- Version
- 1.0.2
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP
- Published
- 2026-06-22
- Updated
- 2026-06-22
- Publisher
- trade.rubin
- Namespace
- Namespace verified by the MCP Registry via the domain rubin.trade · how
- Website
- code.rubin.trade/ai
- Repository
- github.com/rubin-trade/rubin-mainnet-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.mainnet.rubin.trade/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- ritbit-mcp 0.2.0 · protocol 2025-06-18
- Tools discovered
33 - show names
whoami,get_block_height,list_markets,get_market,get_orderbook,get_candles,get_candles_multi,get_balance,get_equity,get_positions,get_open_orders,get_portfolio,get_position_risk,get_fills,get_pnl,get_funding_status,deposit_to_subaccount,top_up_gas,place_limit_order,place_market_order,cancel_order,cancel_all_orders,batch_cancel,place_stop_loss,place_take_profit,close_position,close_all_positions,open_position,get_news,get_leaderboard,get_my_rank,get_fee_tier,get_referral_program- Checked on
- 2026-10-05
How to connect Rubin Exchange
Rubin Exchange is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.mainnet.rubin.trade/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More finance servers
| Server | Runs |
|---|---|
| Roraima for hostsHosts: read bookings, listings, devices and credits; change prices and seasons. No payments. | Remote · HTTPLive check: sign-in required |
| RoutescoreRead-only pre-sign evidence for onchain agents: route quality, MEV exposure, clear/caution verdict. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| ru-marketplace-mcpRead-only MCP servers for Russian marketplaces: prices, stock, ratings, reviews, seller identity. | Local · stdio |
| Ruben Marcus - Agent-Ready PortfolioPublic portfolio MCP for resume, services, availability, project evidence, and introductions. | Remote · HTTPLive check: ✓ handshake |
| Rubric MCPAttested evidence tools for AI agents: sanctions screening, agent/wallet records, paid via x402. | Local · stdio |
| Rug Munch MCPCrypto risk intelligence: 19 tools for rug pull detection, AI forensics, and token analysis. | Local · stdio |
| Rugcheck AiSolana token safety for AI agents - rug-pull, honeypot & Token-2022 trap detection before you buy. | Remote · HTTPLive check: ✗ no handshake |
| run.payStripe-native marketplace where AI agents discover and pay per call for API services. | Remote · HTTPLive check: ✓ handshake |