wait_for_report — Ysaere MCP Tool
wait_for_report
(wait for report) is one of 22 tools on the
Ysaere
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call wait_for_report from your client
- Claude Code Ysaere wait_for_report run in your project directory
- Claude Desktop Ysaere wait_for_report ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Ysaere wait_for_report ~/.cursor/mcp.json
- VS Code Ysaere wait_for_report .vscode/mcp.json
- Zed Ysaere wait_for_report ~/.config/zed/settings.json
- Windsurf Ysaere wait_for_report ~/.codeium/windsurf/mcp_config.json
- Cline Ysaere wait_for_report ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Ysaere wait_for_report ~/.gemini/settings.json
- Grok Ysaere wait_for_report .mcp.json (in your project root)
- ChatGPT Ysaere wait_for_report Settings → Connectors → Advanced → Developer mode
- Claude.ai Ysaere wait_for_report Settings → Connectors → Add custom connector
- LangChain Ysaere wait_for_report pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.ysaere.com/mcpOther tools on this server
- company_intelligence
- competitive_intelligence
- market_intelligence
- angel_intelligence
- angel_deep_intelligence
- due_diligence
- security_assessment
- sourced_brief
- vault_search
- kyb_verify
- quick_brief
- classify_entities
- company_snapshot
- notary_hash
- check_report_status
- verify_provenance
- check_balance
- estimate_credits
- frontdoor_find_local_service
- frontdoor_get_business
- frontdoor_request_booking
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.