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