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