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