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