check_site — GearHost MCP Tool Read-only
check_site
(check site) is one of 20 tools on the
GearHost
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_site from your client
- Claude Code GearHost check_site run in your project directory
- Claude Desktop GearHost check_site ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GearHost check_site ~/.cursor/mcp.json
- VS Code GearHost check_site .vscode/mcp.json
- Zed GearHost check_site ~/.config/zed/settings.json
- Windsurf GearHost check_site ~/.codeium/windsurf/mcp_config.json
- Cline GearHost check_site ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GearHost check_site ~/.gemini/settings.json
- Grok GearHost check_site .mcp.json (in your project root)
- ChatGPT GearHost check_site Settings → Connectors → Advanced → Developer mode
- Claude.ai GearHost check_site Settings → Connectors → Add custom connector
- LangChain GearHost check_site pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.gearhost.com/Other tools on this server
- publish_website
- get_publish_info
- get_plans
- unpublish_website
- get_site_status
- report_abuse
- list_my_previews
- get_domain_setup
- get_domain_status
- get_claim_status
- list_versions
- rollback_website
- list_my_sites
- list_form_messages
- get_site_stats
- publish_to_my_site
- delete_my_site
- attach_custom_domain
- claim_website
This list was read from the server itself, by connecting to it and calling tools/list on 10 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.