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