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