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