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

BOB Gateway

REMOTE · MCP.GOBOB.XYZ

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

Available components

65 Trust /100

Last scanned (12 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 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.

  • 19 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 18 Nov 26 64

    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 21 Nov 2026 · Probed https://mcp.gobob.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=gobob.xyz CN=WE1,O=Google Trust Services,C=US 24 Sept 2026 23 Dec 2026 ECDSA 256 ECDSA-SHA256 dc1a501cdc5c33231360c7dd97c12ae7
SANs: gobob.xyz, *.gobob.xyz
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.gobob.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
xyz. DS published 3599, 18130 8, 8 Verified
gobob.xyz. No DS 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 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.gobob.xyz/mcp Verified 200
http (plaintext) http://mcp.gobob.xyz/mcp HTTPS enforced 301 https://mcp.gobob.xyz/mcp
MCP tools · 9 exposed · ~1,199 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_order ~79

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.

NameTypeReqDescription
quoteobjectyesThe quote object exactly as returned by `get_quote`, e.g. {"onramp": {...}}; not a string

No output schema declared.

No examples provided.

get_max_spendable ~40

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

NameTypeReqDescription
addressstringyesBitcoin address

No output schema declared.

No examples provided.

get_order ~37

Get an order's status and details.

NameTypeReqDescription
idstringyesOrder id, source Bitcoin txid, or source EVM tx hash

No output schema declared.

No examples provided.

get_orders ~69

List orders for one or more user addresses, paginated.

NameTypeReqDescription
cursorstring|null–Cursor from a previous response's `nextCursor`
limitinteger|null–Page size
user_addressesarrayyesUser addresses (up to 20), each encoded for its own chain

No output schema declared.

No examples provided.

get_quote ~345

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

NameTypeReqDescription
affiliatesstring|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.
amountstringyesAmount to swap as an integer string in the source token's smallest unit
dst_chainstringyesDestination chain
dst_tokenstringyesDestination token address; "0x0000000000000000000000000000000000000000" for BTC/native
recipientstringyesAddress receiving the funds, encoded for the destination chain
refund_addressstring|null–Refund address on the source chain. Optional here, required by create-order.
senderstring|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…
slippageinteger|null–Slippage tolerance in basis points (max 1000). Omit to let the gateway pick one per route.
src_chainstringyesSource chain, e.g. "bitcoin", "ethereum", "base", "bob", "tron"
src_tokenstringyesSource token address; "0x0000000000000000000000000000000000000000" for BTC/native

No output schema declared.

No examples provided.

get_routes ~61

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

NameTypeReqDescription
dst_chainstring|null–Only routes to this chain, e.g. "ethereum"
src_chainstring|null–Only routes from this chain, e.g. "bitcoin"

No output schema declared.

No examples provided.

quote_and_create ~376

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.

NameTypeReqDescription
affiliatesstring|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.
amountstringyesAmount to swap as an integer string in the source token's smallest unit
dst_chainstringyesDestination chain
dst_tokenstringyesDestination token address; "0x0000000000000000000000000000000000000000" for BTC/native
recipientstringyesAddress receiving the funds, encoded for the destination chain
refund_addressstringyesRefund address on the source chain
senderstring|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…
slippageinteger|null–Slippage tolerance in basis points (max 1000). Omit to let the gateway pick one per route.
src_chainstringyesSource chain, e.g. "bitcoin", "ethereum", "base", "bob", "tron"
src_tokenstringyesSource token address; "0x0000000000000000000000000000000000000000" for BTC/native

No output schema declared.

No examples provided.

register_tx ~81

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

NameTypeReqDescription
bitcoin_tx_hexstringyesHex-encoded, fully signed Bitcoin transaction paying the order's deposit address
order_idstringyesOnramp order id returned by `create_order`

No output schema declared.

No examples provided.

wait_for_order ~111

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.

NameTypeReqDescription
idstringyesOrder id, source Bitcoin txid, or source EVM tx hash

No output schema declared.

No examples provided.

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.

remote · mcp.gobob.xyz

# add to Claude Code
claude mcp add --transport http xyz-gobob-gateway 'https://mcp.gobob.xyz/mcp'
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.