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