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