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.

Gate Exchange MCP

REMOTE · API.GATEMCP.AI · SCANNED SEP 20

OAuth Gate exchange MCP for CEX trading, account, wallet, unified account, and sub-account.

Available components

−13 this week 18 Trust /100
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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the Gate Exchange MCP server?

Gate Exchange MCP is a hosted endpoint at https://api.gatemcp.ai/mcp/exchange, 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 · api.gatemcp.ai

# add to Claude Code
claude mcp add --transport http gateio-dev-gate-exchange 'https://api.gatemcp.ai/mcp/exchange'
// .cursor/mcp.json
{
  "mcpServers": {
    "gateio-dev-gate-exchange": {
      "url": "https://api.gatemcp.ai/mcp/exchange"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "gateio-dev-gate-exchange": {
      "type": "http",
      "url": "https://api.gatemcp.ai/mcp/exchange"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.gateio-dev-gate-exchange]
url = "https://api.gatemcp.ai/mcp/exchange"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gateio-dev-gate-exchange": {
      "type": "remote",
      "url": "https://api.gatemcp.ai/mcp/exchange",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add gateio-dev-gate-exchange --url 'https://api.gatemcp.ai/mcp/exchange' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  gateio-dev-gate-exchange:
    url: "https://api.gatemcp.ai/mcp/exchange"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "gateio-dev-gate-exchange": {
      "Transport": "http",
      "Url": "https://api.gatemcp.ai/mcp/exchange"
    }
  }
}
# add to Vellum
assistant mcp add gateio-dev-gate-exchange -t streamable-http -u 'https://api.gatemcp.ai/mcp/exchange'
// mcp.json
{
  "mcpServers": {
    "gateio-dev-gate-exchange": {
      "type": "http",
      "url": "https://api.gatemcp.ai/mcp/exchange"
    }
  }
}

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

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.

  • 17 Sept 26 −13
    • Transport: unverified → fail security
    • Authorization: pass → unverified security
    • Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools. security
    • Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
    • Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • HTTPS: pass → unverified security
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    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 20 Sept 2026 · Probed https://api.gatemcp.ai/mcp/exchange

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.gatemcp.ai CN=TrustAsia DV TLS RSA CA 2025,O=TrustAsia Technologies\, Inc.,C=CN 1 Aug 2026 29 Oct 2026 RSA 2048 SHA256-RSA 5b67f0c347846bf3451b522c6ab8381
SANs: api.gatemcp.ai
CN=TrustAsia DV TLS RSA CA 2025,O=TrustAsia Technologies\, Inc.,C=CN (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 8 Jan 2025 7 Jan 2035 RSA 4096 SHA256-RSA 926323b4964e368461512def1a5d52c
CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 1 Aug 2013 15 Jan 2038 RSA 2048 SHA256-RSA 33af1e6a711a9a0bb2864b11d09fae5

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.gatemcp.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
gatemcp.ai. absent 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 404

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.gatemcp.ai/mcp/exchange HTTP error 404
http (plaintext) http://api.gatemcp.ai/mcp/exchange Inconclusive 404
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Common questions

What is the Gate Exchange MCP server?

Gate Exchange MCP is listed in the public MCP registry as io.github.gateio-dev/gate-exchange. OAuth Gate exchange MCP for CEX trading, account, wallet, unified account, and sub-account. This page covers its hosted endpoint (https://api.gatemcp.ai/mcp/exchange).

Is the Gate Exchange MCP server safe to use?

Gate Exchange MCP scores 18 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.

Does the Gate Exchange MCP server require authentication?

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

Is the Gate Exchange MCP server still maintained?

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