# RocketChange exchange (remote · rocketchange.io)

Crypto and fiat exchange rates, limits and ready exchange links on rocketchange.io.

- Trust score: 58/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `rocketchange.io`: 58/100 (this document), [markdown](https://verifymcp.io/servers/io-rocketchange-exchange/rocketchange.md), [page](https://verifymcp.io/servers/io-rocketchange-exchange/rocketchange)

## Channel facts

- Endpoint: `https://rocketchange.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 667 tokens (~133/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "list_pay_methods" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the RocketChange exchange MCP server?

RocketChange exchange is a hosted endpoint at https://rocketchange.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-rocketchange-exchange 'https://rocketchange.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-rocketchange-exchange": {
      "url": "https://rocketchange.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-rocketchange-exchange": {
      "type": "http",
      "url": "https://rocketchange.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-rocketchange-exchange]
url = "https://rocketchange.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-rocketchange-exchange": {
      "type": "remote",
      "url": "https://rocketchange.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-rocketchange-exchange --url 'https://rocketchange.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-rocketchange-exchange:
    url: "https://rocketchange.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-rocketchange-exchange": {
      "Transport": "http",
      "Url": "https://rocketchange.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-rocketchange-exchange -t streamable-http -u 'https://rocketchange.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-rocketchange-exchange": {
      "type": "http",
      "url": "https://rocketchange.io/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 58, +1)

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

### 2026-11-02 (score 57, +1)

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

### 2026-10-30 (score 56, +1)

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

### 2026-10-29 (score 55, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-28 (score 55, +1)

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

### 2026-10-26 (score 54, +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.

### 2026-10-25 (score 53, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 53)

First indexed and scored.

## MCP tools (5)

### `list_pay_methods` (~92 tokens)

Pay methods of the exchange: what the client can give (pay with) and receive.

        Each method has a `code` used by the other tools. `search` filters by
        name, currency, code or network (e.g. "USDT", "Monobank", "TRC20").

Input parameters:

- `lang` (string)
- `search`
- `side` (string)

### `list_receive_options` (~45 tokens)

What the client can receive for the method they give (by its `code`).

Input parameters:

- `give` (string, required)
- `lang` (string)
- `search`

### `get_quote` (~151 tokens)

A quote for an exchange and the link to make it on the site.

        `give` and `receive` are method codes; `amount` is what the client gives
        (amount_side="give") or wants to receive (amount_side="receive"). Returns
        both amounts, the rate, the limits, the requisites the site will ask for
        and `exchange_link`: the site's exchange form with all this filled in,
        where the person enters the e-mail and requisites and creates the bid.

Input parameters:

- `amount` (number, required)
- `amount_side` (string)
- `give` (string, required)
- `lang` (string)
- `receive` (string, required)

### `about_exchange` (~38 tokens)

The exchange itself: the site, terms, support, and the independent
        monitors and review sites listing it (its rating and reviews are there).

### `get_reserves` (~32 tokens)

How much of each currency the exchange can pay out now (by currency, then method).

Input parameters:

- `currency`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-rocketchange-exchange/rocketchange#diagnostics

## Score history

- 2026-11-05: 58
- 2026-11-04: 58
- 2026-11-03: 57
- 2026-11-02: 57
- 2026-11-01: 56
- 2026-10-31: 56
- 2026-10-30: 56
- 2026-10-29: 55
- 2026-10-28: 55
- 2026-10-27: 54
- 2026-10-26: 54
- 2026-10-25: 53
- 2026-10-24: 53

## Common questions

### What is the RocketChange exchange MCP server?

RocketChange exchange is an MCP server listed in the public MCP registry as io.rocketchange/exchange. Crypto and fiat exchange rates, limits and ready exchange links on rocketchange.io. This page covers its hosted endpoint (https://rocketchange.io/mcp).

### Is the RocketChange exchange MCP server safe to use?

RocketChange exchange scores 58 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the RocketChange exchange MCP server expose?

RocketChange exchange exposes 5 tools: list_pay_methods, list_receive_options, get_quote, about_exchange, get_reserves. Their descriptions and schemas cost roughly 358 tokens of context every time the server is loaded.

### Does the RocketChange exchange MCP server require authentication?

No. We connected to RocketChange exchange without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RocketChange exchange MCP server still maintained?

RocketChange exchange is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://rocketchange.io/mcp
- Website: https://rocketchange.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-rocketchange-exchange/rocketchange.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-rocketchange-exchange/rocketchange.json
- HTML version of this page: https://verifymcp.io/servers/io-rocketchange-exchange/rocketchange