verdict_chain — Did It Work? MCP Tool
verdict_chain
(verdict chain) is one of 22 tools on the
Did It Work?
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verdict_chain from your client
- Claude Code Did It Work? verdict_chain run in your project directory
- Claude Desktop Did It Work? verdict_chain ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Did It Work? verdict_chain ~/.cursor/mcp.json
- VS Code Did It Work? verdict_chain .vscode/mcp.json
- Zed Did It Work? verdict_chain ~/.config/zed/settings.json
- Windsurf Did It Work? verdict_chain ~/.codeium/windsurf/mcp_config.json
- Cline Did It Work? verdict_chain ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Did It Work? verdict_chain ~/.gemini/settings.json
- Grok Did It Work? verdict_chain .mcp.json (in your project root)
- ChatGPT Did It Work? verdict_chain Settings → Connectors → Advanced → Developer mode
- Claude.ai Did It Work? verdict_chain Settings → Connectors → Add custom connector
- LangChain Did It Work? verdict_chain pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http did-it-work https://api.diditwork.org/mcpOther tools on this server
- decision_brief
- recommend_charity
- list_charities
- search_orgs
- get_org
- compare_charities
- estimate_impact
- report_decision_effect
- list_leaderboards
- get_review_queue
- get_trust
- get_tax
- allocate_portfolio
- create_giving_intent
- list_claims
- get_claim
- list_values_profiles
- get_values_profile
- list_ledger_records
- get_ledger_record
- get_meta
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.