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