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