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