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