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