Finance · Remote MCP server
xRocket Exchange MCP
Autonomous xRocket CEX trading inside operator-set limits, plus live market data over MCP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.nakazanie-ton/xrocket- Version
- 0.6.0
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-08-25
- Updated
- 2026-08-25
- Publisher
- nakazanie-ton (GitHub)
- Website
- xrocket-mcp-production.up.railway.app/
- Repository
- github.com/nakazanie-ton/myrocket (folder plugins/xrocket-exchange)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://xrocket-mcp-production.up.railway.app/mcp | None |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | xrocket-mcp | 0.6.0 | stdio |
How to connect xRocket Exchange MCP
xRocket Exchange MCP is a remote MCP server: there is nothing to install. Its endpoint is https://xrocket-mcp-production.up.railway.app/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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: xrocket-mcp version 0.6.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y xrocket-mcp@0.6.0. It reads these environment variables: XROCKET_PROFILE, XROCKET_ENVIRONMENT, XROCKET_API_TOKEN (secret), XROCKET_ENABLE_TRADING, XROCKET_TRADING_LIMIT, XROCKET_ENABLE_TRANSFERS, XROCKET_ENABLE_WITHDRAWALS, XROCKET_ALLOW_MAINNET_WRITES and XROCKET_APPROVAL_TTL_MS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"xrocket": {
"command": "npx",
"args": [
"-y",
"xrocket-mcp@0.6.0"
],
"env": {
"XROCKET_PROFILE": "<value>",
"XROCKET_ENVIRONMENT": "<value>",
"XROCKET_API_TOKEN": "<secret>",
"XROCKET_ENABLE_TRADING": "<value>",
"XROCKET_TRADING_LIMIT": "<value>",
"XROCKET_ENABLE_TRANSFERS": "<value>",
"XROCKET_ENABLE_WITHDRAWALS": "<value>",
"XROCKET_ALLOW_MAINNET_WRITES": "<value>",
"XROCKET_APPROVAL_TTL_MS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. 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 |
|---|---|
| xpay Lead Gen50+ lead gen tools. Apollo, Hunter, Nyne, Tomba, Sixtyfour, Fiber, Exa. Pay-per-use via x402. | Remote · HTTP |
| Xpex Plugin FactoryMCP plugin factory and x402 Agent Kit API for external agents, at 0.01 USDC per call. | Remote · HTTP |
| xProofProof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs. | Remote · HTTP |
| Xrechnung MCPValidate and parse German e-invoices (XRechnung, ZUGFeRD, Factur-X) offline. No API key. | Local · stdio |
| Xrpl RefereeTrust and payment layer for the agentic economy on the XRP Ledger. | Remote · HTTP |
| XRPL Wallet Risk ScoreXRPL wallet risk scoring. Behavioral tags, sub-scores, graph analysis. Pay per call in XRP. | Local · stdio |
| XRPL-UtilitiesXRPL data tools for AI agents: wallet classifier, signals, RWA tracker, ETF flows. Pay via x402. | Local · stdio |
| xrpldashboardRead-only XRP Ledger MCP tools with proof-annotation envelopes and signed daily snapshots. | Remote · HTTP |