# BOB Gateway (remote · mcp.gobob.xyz)

Swap native BTC to and from tokens on EVM chains and Tron through BOB Gateway

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.gobob.xyz`: 65/100 (this document), [markdown](https://verifymcp.io/servers/xyz-gobob-gateway/mcp.md), [page](https://verifymcp.io/servers/xyz-gobob-gateway/mcp)

## Channel facts

- Endpoint: `https://mcp.gobob.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (register_tx).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2215 tokens (~246/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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 BOB Gateway MCP server?

BOB Gateway is a hosted endpoint at https://mcp.gobob.xyz/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 xyz-gobob-gateway 'https://mcp.gobob.xyz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-gobob-gateway": {
      "url": "https://mcp.gobob.xyz/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-gobob-gateway": {
      "type": "http",
      "url": "https://mcp.gobob.xyz/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xyz-gobob-gateway]
url = "https://mcp.gobob.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-gobob-gateway": {
      "type": "remote",
      "url": "https://mcp.gobob.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-gobob-gateway --url 'https://mcp.gobob.xyz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-gobob-gateway:
    url: "https://mcp.gobob.xyz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-gobob-gateway": {
      "Transport": "http",
      "Url": "https://mcp.gobob.xyz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-gobob-gateway -t streamable-http -u 'https://mcp.gobob.xyz/mcp'
```

### Other

```json
{
  "mcpServers": {
    "xyz-gobob-gateway": {
      "type": "http",
      "url": "https://mcp.gobob.xyz/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-20 (score 65, +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-11-19 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-18 (score 64)

First indexed and scored.

## MCP tools (9)

### `create_order` (~79 tokens)

Create an order from a quote. Returns the order id plus what the user must sign: a
deposit address / PSBT for onramps, or the EVM or Tron transaction otherwise.

Input parameters:

- `quote` (object, required): The quote object exactly as returned by `get_quote`, e.g. {"onramp": {...}}; not a string

### `get_max_spendable` (~40 tokens)

Maximum BTC (sats) an address can send to an onramp after estimated network fees.

Input parameters:

- `address` (string, required): Bitcoin address

### `get_order` (~37 tokens)

Get an order's status and details.

Input parameters:

- `id` (string, required): Order id, source Bitcoin txid, or source EVM tx hash

### `get_orders` (~69 tokens)

List orders for one or more user addresses, paginated.

Input parameters:

- `cursor` (string|null): Cursor from a previous response's `nextCursor`
- `limit` (integer|null): Page size
- `user_addresses` (array, required): User addresses (up to 20), each encoded for its own chain

### `get_quote` (~345 tokens)

Get a quote for a swap (onramp quotes are signed by the API). Pass the returned object
unchanged to `create_order`.

Input parameters:

- `affiliates` (string|null): Affiliate fees as comma-separated `<address>:<bps>` pairs, e.g. "0xabc...:50". Addresses are EVM, except on a token swap to Tron, where a Tron address is also accepted.
- `amount` (string, required): Amount to swap as an integer string in the source token's smallest unit
- `dst_chain` (string, required): Destination chain
- `dst_token` (string, required): Destination token address; "0x0000000000000000000000000000000000000000" for BTC/native
- `recipient` (string, required): Address receiving the funds, encoded for the destination chain
- `refund_address` (string|null): Refund address on the source chain. Optional here, required by create-order.
- `sender` (string|null): Address sending the funds, encoded for the source chain. On onramps it lets create-order return a funded PSBT, which may spend the address's ordinals, inscriptions or runes as plain sats: omit it for…
- `slippage` (integer|null): Slippage tolerance in basis points (max 1000). Omit to let the gateway pick one per route.
- `src_chain` (string, required): Source chain, e.g. "bitcoin", "ethereum", "base", "bob", "tron"
- `src_token` (string, required): Source token address; "0x0000000000000000000000000000000000000000" for BTC/native

### `get_routes` (~61 tokens)

List supported swap routes (source/destination chain and token pairs).

Input parameters:

- `dst_chain` (string|null): Only routes to this chain, e.g. "ethereum"
- `src_chain` (string|null): Only routes from this chain, e.g. "bitcoin"

### `quote_and_create` (~376 tokens)

Get a quote and create an order from it in one call, returning both as `quote` and
\`order`. Takes the `get_quote` arguments, with `refund_address` required. Creating an
order screens its addresses, so use this only once the user wants to swap, and `get_quote`
to check a price.

Input parameters:

- `affiliates` (string|null): Affiliate fees as comma-separated `<address>:<bps>` pairs, e.g. "0xabc...:50". Addresses are EVM, except on a token swap to Tron, where a Tron address is also accepted.
- `amount` (string, required): Amount to swap as an integer string in the source token's smallest unit
- `dst_chain` (string, required): Destination chain
- `dst_token` (string, required): Destination token address; "0x0000000000000000000000000000000000000000" for BTC/native
- `recipient` (string, required): Address receiving the funds, encoded for the destination chain
- `refund_address` (string, required): Refund address on the source chain
- `sender` (string|null): Address sending the funds, encoded for the source chain. On onramps it lets create-order return a funded PSBT, which may spend the address's ordinals, inscriptions or runes as plain sats: omit it for…
- `slippage` (integer|null): Slippage tolerance in basis points (max 1000). Omit to let the gateway pick one per route.
- `src_chain` (string, required): Source chain, e.g. "bitcoin", "ethereum", "base", "bob", "tron"
- `src_token` (string, required): Source token address; "0x0000000000000000000000000000000000000000" for BTC/native

### `register_tx` (~81 tokens)

Broadcast an already-signed onramp Bitcoin transaction through the gateway. Optional:
deposits are detected on-chain without it. The broadcast cannot be undone.

Input parameters:

- `bitcoin_tx_hex` (string, required): Hex-encoded, fully signed Bitcoin transaction paying the order's deposit address
- `order_id` (string, required): Onramp order id returned by `create_order`

### `wait_for_order` (~111 tokens)

Wait for an order's status to leave `inProgress`, reading it every 15 seconds for up to
about 45. Returns the order as `get_order` does, as soon as its status changes or once
the wait is over; call again while it is still `inProgress`. Under heavy load it may
return after a single read. Reports progress when the client asks for it.

Input parameters:

- `id` (string, required): Order id, source Bitcoin txid, or source EVM tx hash

## Diagnostics

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

## Score history

- 2026-11-21: 65
- 2026-11-20: 65
- 2026-11-19: 64
- 2026-11-18: 64

## Common questions

### What is the BOB Gateway MCP server?

BOB Gateway is an MCP server listed in the public MCP registry as xyz.gobob/gateway. Swap native BTC to and from tokens on EVM chains and Tron through BOB Gateway. This page covers its hosted endpoint (https://mcp.gobob.xyz/mcp).

### Is the BOB Gateway MCP server safe to use?

BOB Gateway scores 65 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 BOB Gateway MCP server expose?

BOB Gateway exposes 9 tools: create_order, get_max_spendable, get_order, get_orders, get_quote, and 4 more. Their descriptions and schemas cost roughly 1,199 tokens of context every time the server is loaded.

### Does the BOB Gateway MCP server require authentication?

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

### Is the BOB Gateway MCP server still maintained?

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

### What did VerifyMCP test on the BOB Gateway MCP server?

VerifyMCP ran 13 checks on BOB Gateway, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.gobob.xyz/mcp
- Website: https://docs.gobob.xyz/gateway/agents
- Changelog RSS feed: https://verifymcp.io/servers/xyz-gobob-gateway/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-gobob-gateway/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/xyz-gobob-gateway/mcp.json
- HTML version of this page: https://verifymcp.io/servers/xyz-gobob-gateway/mcp
