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