verify_stake_bet — stake analyzer MCP Prompt
verify_stake_bet
is one of 2 prompts on the
stake analyzer
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke verify_stake_bet from your client
- Claude Code stake analyzer Prompt/verify_stake_bet run in your project directory
- Claude Desktop stake analyzer Prompt/verify_stake_bet ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor stake analyzer Prompt/verify_stake_bet ~/.cursor/mcp.json
- VS Code stake analyzer Prompt/verify_stake_bet .vscode/mcp.json
- Zed stake analyzer Prompt/verify_stake_bet ~/.config/zed/settings.json
- Windsurf stake analyzer Prompt/verify_stake_bet ~/.codeium/windsurf/mcp_config.json
- Cline stake analyzer Prompt/verify_stake_bet ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI stake analyzer Prompt/verify_stake_bet ~/.gemini/settings.json
- Grok stake analyzer Prompt/verify_stake_bet .mcp.json (in your project root)
- ChatGPT stake analyzer Prompt/verify_stake_bet Settings → Connectors → Advanced → Developer mode
- Claude.ai stake analyzer Prompt/verify_stake_bet Settings → Connectors → Add custom connector
- LangChain stake analyzer Prompt/verify_stake_bet pip install langchain-mcp-adapters
Other prompts on this server
Read from the server itself, by connecting to it and calling prompts/list on 11 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.