Skip to content

Click Decay MCP server

com.clickdecay/mcp-serverclickdecay.comstreamable-httpv1.0.0Scanned

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

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Click Decay MCP server can do

The Click Decay MCP server is published by clickdecay.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: project_clicks_at_ctr and impressions_needed_for_clicks), but cannot delete data. 2 tools only read.

1 tool brings in text other people can write (check_gsc_reporting_issues).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • impressions_needed_for_clicksCalculates how many impressions a click target needs at a CTR you choose (clicks ÷ CTR).1 finding

    Why it is in this group

    • The name "impressions_needed_for_clicks" says "click": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "impressions_needed_for_clicks" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "impressions_needed_for_clicks" says "click": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Calculates 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • project_clicks_at_ctrCalculates the clicks a number of impressions would earn at a CTR you choose (impressions × CTR).1 finding

    Why it is in this group

    • The name "project_clicks_at_ctr" says "click": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "project_clicks_at_ctr" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "project_clicks_at_ctr" says "click": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Calculates 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • 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 t…Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • untrusted-inputThe name "check_gsc_reporting_issues" says "issue": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • compare_ctr_periodsCompares clicks, impressions and CTR of two equal-length, non-overlapping periods whose totals you provide, for example from Google Search Console.No findings

    Why it is in this group

    • The name "compare_ctr_periods" says "compare": a word for reading.
    Description, as the server wrote it
    Compares 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:21 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://clickdecay.com/mcp: tools/list returned 4 tools to an anonymous client, including project_clicks_at_ctr (write), impressions_needed_for_clicks (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "project_clicks_at_ctr" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "project_clicks_at_ctr" says "click": a word for a change.

    What this check looks for
  • The server marks "impressions_needed_for_clicks" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "impressions_needed_for_clicks" says "click": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__clickdecay__compare_ctr_periods",
      "mcp__clickdecay__check_gsc_reporting_issues"
    ],
    "ask": [
      "mcp__clickdecay__project_clicks_at_ctr",
      "mcp__clickdecay__impressions_needed_for_clicks"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as clickdecay. Review it before you use it.

Capability tags behind 1 rule
  • mcp__clickdecay__check_gsc_reporting_issues untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.clickdecay/mcp-server/verify?hash=f1642b0f574f5fcbc301daa65734e54b4bff359d03ab18b1d36d71e069b81a4d" | jq -e '.changed == false'

Pinned hash f1642b0f574f, from Nov 12, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.clickdecay/mcp-server/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.clickdecay/mcp-server
[![Anlyon Radar](https://radar.anlyon.com/badge/com.clickdecay/mcp-server.svg)](https://radar.anlyon.com/servers/com.clickdecay/mcp-server)

Source: MCP Registry · repository. Synced Nov 13, 2026, 00:17 UTC.

Click Decay MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Click Decay MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Click Decay MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Click Decay MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Click Decay MCP server have?

4 tools: 2 write, 2 read. project_clicks_at_ctr, impressions_needed_for_clicks, compare_ctr_periods and check_gsc_reporting_issues.

Does the Click Decay MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Click Decay MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Click Decay MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.