derive_kill_criteria — ideaudit MCP Tool
derive_kill_criteria
(derive kill criteria) is one of 21 tools on the
ideaudit
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call derive_kill_criteria from your client
- Claude Code ideaudit derive_kill_criteria run in your project directory
- Claude Desktop ideaudit derive_kill_criteria ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ideaudit derive_kill_criteria ~/.cursor/mcp.json
- VS Code ideaudit derive_kill_criteria .vscode/mcp.json
- Zed ideaudit derive_kill_criteria ~/.config/zed/settings.json
- Windsurf ideaudit derive_kill_criteria ~/.codeium/windsurf/mcp_config.json
- Cline ideaudit derive_kill_criteria ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ideaudit derive_kill_criteria ~/.gemini/settings.json
- Grok ideaudit derive_kill_criteria .mcp.json (in your project root)
- ChatGPT ideaudit derive_kill_criteria Settings → Connectors → Advanced → Developer mode
- Claude.ai ideaudit derive_kill_criteria Settings → Connectors → Add custom connector
- LangChain ideaudit derive_kill_criteria pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ideaudit-tools https://api.inite.studio/mcp
Other tools on this server
- get_started
- compute_barrier
- compute_budget_proof
- compute_build_complexity
- compute_collection_scores
- compute_crossed_matrix
- compute_dealbreakers_v2
- compute_funding_momentum
- compute_hiring_demand
- compute_lrs_composite_v2
- compute_lrs_composite
- compute_monetization
- compute_multi_source_tam
- compute_ppc_spend_signal
- compute_search_velocity_v2
- compute_search_velocity
- compute_social_pain
- compute_urgency_composite
- compute_x_signal
- validate_unit_economics
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.