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