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