lookup_tracker — movahedi.ca Privacy Data MCP Tool Read-only
lookup_tracker
(lookup tracker) is one of 14 tools on the
movahedi.ca Privacy Data
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call lookup_tracker from your client
- Claude Code movahedi.ca Privacy Data lookup_tracker run in your project directory
- Claude Desktop movahedi.ca Privacy Data lookup_tracker ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor movahedi.ca Privacy Data lookup_tracker ~/.cursor/mcp.json
- VS Code movahedi.ca Privacy Data lookup_tracker .vscode/mcp.json
- Zed movahedi.ca Privacy Data lookup_tracker ~/.config/zed/settings.json
- Windsurf movahedi.ca Privacy Data lookup_tracker ~/.codeium/windsurf/mcp_config.json
- Cline movahedi.ca Privacy Data lookup_tracker ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI movahedi.ca Privacy Data lookup_tracker ~/.gemini/settings.json
- Grok movahedi.ca Privacy Data lookup_tracker .mcp.json (in your project root)
- ChatGPT movahedi.ca Privacy Data lookup_tracker Settings → Connectors → Advanced → Developer mode
- Claude.ai movahedi.ca Privacy Data lookup_tracker Settings → Connectors → Add custom connector
- LangChain movahedi.ca Privacy Data lookup_tracker pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http privacy https://movahedi.ca/mcpOther tools on this server
- privacy_search_enforcement_actions
- privacy_get_enforcement_case
- privacy_lookup_glossary_term
- privacy_list_glossary_terms
- privacy_law25_requirements
- classify_cookie
- lookup_crawler
- list_crawlers
- privacy_get_a2ui_card
- privacy_search_api
- privacy_execute_plan
- canadian_privacy_consequential_action_lookup_v1
- canadian_privacy_breach_deadline_calculator_v1
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.