Skip to main content

Click Decay

com.clickdecay/mcp-serverVersion 1.0.0

CTR change, click decomposition and known Search Console data anomalies for numbers you provide.

Status

Responds338 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 13:51 UTC
Latency
338 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://clickdecay.com/mcpResponds338 ms
No sign-in

Claude Code

claude mcp add --transport http mcp-server https://clickdecay.com/mcp

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: mcp-server
Remote MCP server URL: https://clickdecay.com/mcp

Cursor

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://clickdecay.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"mcp-server","type":"http","url":"https://clickdecay.com/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

4 tools

Tools of Click Decay
Read-only
Idempotent
Open world
check_gsc_reporting_issuesLists the known Google Search Console reporting issues, taken from Google's own notices, that overlap the dates you give, with the affected metrics, the sources they apply to and the source link. Without dates it lists every known issue. compare_ctr_periods runs the same check on its own periods; this tool is for dates you compare elsewhere.NoYesYesNo
compare_ctr_periodsCompares clicks, impressions and CTR of two equal-length, non-overlapping periods whose totals you provide, for example from Google Search Console. It splits the click change into an impressions component and a CTR component and checks the dates against known Search Console reporting issues, withholding impression-based figures for affected dates. Use it when you have totals for two periods; for a single what-if, project_clicks_at_ctr and impressions_needed_for_clicks fit better. The result does not establish why CTR changed; the warning NO_AI_CAUSATION is always included.NoYesYesNo
impressions_needed_for_clicksCalculates how many impressions a click target needs at a CTR you choose (clicks ÷ CTR). Use it to size a goal; project_clicks_at_ctr goes the other way. The result is a modelled value. With a CTR of 0 there is no answer, and the result gives the reason instead of a number.NoYesYesNo
project_clicks_at_ctrCalculates the clicks a number of impressions would earn at a CTR you choose (impressions × CTR). Use it for a what-if on one period; compare_ctr_periods is for two observed periods and impressions_needed_for_clicks for the opposite direction. The result is a modelled value and may be fractional.NoYesYesNo

Details

Registry status
Active
Published
Nov 12, 2026
Updated
Nov 12, 2026
Categories (suggested)
Project managementSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing