verify_license — whoislicensed — state license lookup MCP Tool
verify_license
(verify license) is one of 2 tools on the
whoislicensed — state license lookup
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_license from your client
- Claude Code whoislicensed — state license lookup verify_license run in your project directory
- Claude Desktop whoislicensed — state license lookup verify_license ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor whoislicensed — state license lookup verify_license ~/.cursor/mcp.json
- VS Code whoislicensed — state license lookup verify_license .vscode/mcp.json
- Zed whoislicensed — state license lookup verify_license ~/.config/zed/settings.json
- Windsurf whoislicensed — state license lookup verify_license ~/.codeium/windsurf/mcp_config.json
- Cline whoislicensed — state license lookup verify_license ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI whoislicensed — state license lookup verify_license ~/.gemini/settings.json
- Grok whoislicensed — state license lookup verify_license .mcp.json (in your project root)
- ChatGPT whoislicensed — state license lookup verify_license Settings → Connectors → Advanced → Developer mode
- Claude.ai whoislicensed — state license lookup verify_license Settings → Connectors → Add custom connector
- LangChain whoislicensed — state license lookup verify_license pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http lookup https://whoislicensed.com/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.