Gemini CLI Hive Intelligence MCP check_token_safety

How to: Gemini CLI Hive Intelligence MCP check_token_safety

client:Gemini CLI transport:streamable-http tool:check_token_safety

Add Hive Intelligence MCP to Gemini CLI

01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "mcp": {
      "httpUrl": "https://mcp.hiveintelligence.xyz/mcp"
    }
  }
}

02
Save the file and restart Gemini CLI.
03
Ask for something check_token_safety does. Gemini CLI lists the server's tools on connect and calls check_token_safety itself — you do not invoke it by name.
04
If nothing happens, check the server is running and that Hive Intelligence MCP's identifier in your config matches the one above exactly.

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

Set these first

Hive Intelligence MCP will not start until these are set, so check_token_safety never becomes available.

COINGECKO_PRO_API_KEY
ALCHEMY_API_KEY
GOPLUS_APP_KEY
GOPLUS_APP_SECRET
HELIUS_API_KEY
MORALIS_API_KEY
TENDERLY_API_KEY
TENDERLY_NODE_ACCESS_KEY
TENDERLY_GATEWAY_ACCESS_KEY
TENDERLY_ACCOUNT_SLUG
TENDERLY_PROJECT_SLUG

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

Hive Intelligence MCP MCP server