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