compute_social_pain — ideaudit MCP Tool
compute_social_pain
(compute social pain) 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 compute_social_pain from your client
- Claude Code ideaudit compute_social_pain run in your project directory
- Claude Desktop ideaudit compute_social_pain ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ideaudit compute_social_pain ~/.cursor/mcp.json
- VS Code ideaudit compute_social_pain .vscode/mcp.json
- Zed ideaudit compute_social_pain ~/.config/zed/settings.json
- Windsurf ideaudit compute_social_pain ~/.codeium/windsurf/mcp_config.json
- Cline ideaudit compute_social_pain ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ideaudit compute_social_pain ~/.gemini/settings.json
- Grok ideaudit compute_social_pain .mcp.json (in your project root)
- ChatGPT ideaudit compute_social_pain Settings → Connectors → Advanced → Developer mode
- Claude.ai ideaudit compute_social_pain Settings → Connectors → Add custom connector
- LangChain ideaudit compute_social_pain 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_urgency_composite
- compute_x_signal
- derive_kill_criteria
- 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.