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