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