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