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