scan_token — HexScan Token Security MCP Tool
scan_token
(scan token) is one of 3 tools on the
HexScan Token Security
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 HexScan Token Security scan_token run in your project directory
- Claude Desktop HexScan Token Security scan_token ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor HexScan Token Security scan_token ~/.cursor/mcp.json
- VS Code HexScan Token Security scan_token .vscode/mcp.json
- Zed HexScan Token Security scan_token ~/.config/zed/settings.json
- Windsurf HexScan Token Security scan_token ~/.codeium/windsurf/mcp_config.json
- Cline HexScan Token Security scan_token ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI HexScan Token Security scan_token ~/.gemini/settings.json
- Grok HexScan Token Security scan_token .mcp.json (in your project root)
- ChatGPT HexScan Token Security scan_token Settings → Connectors → Advanced → Developer mode
- Claude.ai HexScan Token Security scan_token Settings → Connectors → Add custom connector
- LangChain HexScan Token Security scan_token pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http token-security https://hexscan.xyz/mcpOther tools on this server
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.