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