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