Home / MCP registry index / io.github.gateio-dev/gate-info
Gate Info MCP
io.github.gateio-dev/gate-info in the official MCP registry.
Endpoint https://api.gatemcp.ai/mcp/info. Source: github.com/gate/gate-mcp.
The registry describes it as: Gate info MCP for coin discovery, market snapshots, technical analysis, and on-chain data.
We read its 32 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
info_coin_get_coin_info info_coin_get_coin_rankings info_coin_search_coins info_compliance_check_token_security info_macro_get_economic_calendar info_macro_get_macro_indicator info_macro_get_macro_summary info_marketdetail_get_kline info_marketdetail_get_orderbook info_marketdetail_get_recent_trades info_marketsnapshot_batch_market_snapshot info_marketsnapshot_get_institutional_metrics info_marketsnapshot_get_market_overview info_marketsnapshot_get_market_snapshot info_markettrend_get_indicator_history info_markettrend_get_kline info_markettrend_get_technical_analysis info_onchain_get_address_info info_onchain_get_address_transactions info_onchain_get_token_onchain info_onchain_get_transaction info_platformmetrics_get_bridge_metrics info_platformmetrics_get_cex_orderbook_depth info_platformmetrics_get_chain_activity info_platformmetrics_get_defi_overview info_platformmetrics_get_exchange_reserves info_platformmetrics_get_liquidation_heatmap info_platformmetrics_get_platform_history info_platformmetrics_get_platform_info info_platformmetrics_get_stablecoin_info info_platformmetrics_get_yield_pools info_platformmetrics_search_platforms
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-gateio-dev-gate-info)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.