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