token_check — sol-defi-desk MCP Tool
token_check
(token check) is one of 4 tools on the
sol-defi-desk
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call token_check from your client
- Claude Code sol-defi-desk token_check run in your project directory
- Claude Desktop sol-defi-desk token_check ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor sol-defi-desk token_check ~/.cursor/mcp.json
- VS Code sol-defi-desk token_check .vscode/mcp.json
- Zed sol-defi-desk token_check ~/.config/zed/settings.json
- Windsurf sol-defi-desk token_check ~/.codeium/windsurf/mcp_config.json
- Cline sol-defi-desk token_check ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI sol-defi-desk token_check ~/.gemini/settings.json
- Grok sol-defi-desk token_check .mcp.json (in your project root)
- ChatGPT sol-defi-desk token_check Settings → Connectors → Advanced → Developer mode
- Claude.ai sol-defi-desk token_check Settings → Connectors → Add custom connector
- LangChain sol-defi-desk token_check pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http sol-defi-desk https://95.216.126.169.sslip.io/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 3 October 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.