get_public_scenario_result — UniBio Intelligence MCP Tool Read-only
get_public_scenario_result
(get public scenario result) is one of 5 tools on the
UniBio Intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_public_scenario_result from your client
- Claude Code UniBio Intelligence get_public_scenario_result run in your project directory
- Claude Desktop UniBio Intelligence get_public_scenario_result ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor UniBio Intelligence get_public_scenario_result ~/.cursor/mcp.json
- VS Code UniBio Intelligence get_public_scenario_result .vscode/mcp.json
- Zed UniBio Intelligence get_public_scenario_result ~/.config/zed/settings.json
- Windsurf UniBio Intelligence get_public_scenario_result ~/.codeium/windsurf/mcp_config.json
- Cline UniBio Intelligence get_public_scenario_result ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI UniBio Intelligence get_public_scenario_result ~/.gemini/settings.json
- Grok UniBio Intelligence get_public_scenario_result .mcp.json (in your project root)
- ChatGPT UniBio Intelligence get_public_scenario_result Settings → Connectors → Advanced → Developer mode
- Claude.ai UniBio Intelligence get_public_scenario_result Settings → Connectors → Add custom connector
- LangChain UniBio Intelligence get_public_scenario_result pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ubi https://mcp.unibiointelligence.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.