get_competitor_scan — Epovest MCP Tool Read-only
get_competitor_scan
(get competitor scan) is one of 67 tools on the
Epovest
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_competitor_scan from your client
- Claude Code Epovest get_competitor_scan run in your project directory
- Claude Desktop Epovest get_competitor_scan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Epovest get_competitor_scan ~/.cursor/mcp.json
- VS Code Epovest get_competitor_scan .vscode/mcp.json
- Zed Epovest get_competitor_scan ~/.config/zed/settings.json
- Windsurf Epovest get_competitor_scan ~/.codeium/windsurf/mcp_config.json
- Cline Epovest get_competitor_scan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Epovest get_competitor_scan ~/.gemini/settings.json
- Grok Epovest get_competitor_scan .mcp.json (in your project root)
- ChatGPT Epovest get_competitor_scan Settings → Connectors → Advanced → Developer mode
- Claude.ai Epovest get_competitor_scan Settings → Connectors → Add custom connector
- LangChain Epovest get_competitor_scan pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ai-visibility https://mcp.epovest.com/mcpOther tools on this server
- list_trackers
- create_tracker
- update_tracker
- start_tracker
- survey_now
- pause_tracker
- archive_tracker
- list_projects
- create_project
- rename_project
- get_canon
- update_project_canon
- get_link_targets
- set_link_targets
- archive_project
- list_surfaces
- create_surface
- update_surface
- tick_surface_checklist
- add_surface_check
- update_surface_check
- delete_surface_check
- restore_surface_check
- delete_surface
- restore_surface
- convert_surface_to_corroboration
- list_corroborations
- create_corroboration
- update_corroboration
- archive_corroboration
- verify_corroboration
- convert_corroboration_to_surface
- list_corroboration_candidates
- dismiss_corroboration_candidate
- get_logbook
- create_logbook_entry
- update_logbook_entry
- delete_logbook_entry
- restore_logbook_entry
- list_quests
- create_quest
- update_quest
- complete_quest
- dismiss_quest
- reopen_quest
- get_results
- get_responses
- list_keyword_discoveries
- accept_keyword_discovery
- dismiss_keyword_discovery
- restore_keyword_discovery
- list_competitor_scans
- create_competitor_scan
- start_competitor_scan
- update_competitor_scan
- list_sources
- get_source
- list_source_channels
- get_account_settings
- update_account_settings
- get_credits
- get_usage
- topup_credits
- contact_support
- list_support_threads
- get_support_thread
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.