Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Data access / search
CTR change, click decomposition and known Search Console data anomalies for numbers you provide.
0 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked . Not enough checks yet| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 4 | 0 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Click Decay
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http click-decay https://clickdecay.com/mcpCapabilities
Lists 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.
DiscoveredCompares 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.
DiscoveredCalculates 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.
DiscoveredCalculates 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.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 82 ms | 4 |