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