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