← Registry

Marketing

whichclick.is

Provides documentation search and tools for generating Google Ads tracking templates and validating WhichClick smart-link routing rules.

1 endpoint5 known toolsFirst detected November 8, 2026Last detected November 8, 2026

ENDPOINT 1

https://app.whichclick.is/api/mcp

No auth detected

MCP server metadata

Name
whichclick
Version
1.0.0
Capabilities
toolsresourcespromptslogging
Server instructions

WhichClick is a Google-certified click tracker, mobile attribution platform (MMP) and click-fraud protection service. Start with search_docs / get_doc for any "how do I" question — the documentation is authoritative. Tools in the read/write scopes need an organization API key (Authorization: Bearer wc_live_…); without one only documentation tools are available. Google Ads transparency rule: the visible url= parameter on GET /c/{slug} is always the next hop, force_transparent=true must be present, and only the first-party click id (default wc_click_id) may be appended. Never suggest adding utm_* or affiliate parameters in the tracker. Writes are scoped to the API key's organization and are recorded in the audit log. Authenticated: no (documentation tools only).

Known tools 5

search_docs

Full-text search over the WhichClick developer documentation.

Inferred read-only
get_doc

Returns one documentation page as Markdown.

Inferred read-only
list_docs

Lists every documentation page grouped by section with a one-line description (same content as /llms.txt).

Inferred read-only
build_tracking_template

Generates a Google Ads tracking template and final URL suffix for a tracking domain + link slug that satisfies Google's transparent click tracker guidelines (visible url= next hop, force_transparent=true, ValueTrack capture).

Inferred read-only
validate_routing_rules

Validates a smart-link rules array and optional settings object against the routing schema and reports errors.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.whichclick]
url = "https://app.whichclick.is/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "whichclick": {
      "type": "http",
      "url": "https://app.whichclick.is/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: whichclick
Remote MCP URL: https://app.whichclick.is/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "whichclick": {
      "url": "https://app.whichclick.is/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "whichclick": {
      "type": "http",
      "url": "https://app.whichclick.is/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "whichclick",
  "transport": "streamable-http",
  "url": "https://app.whichclick.is/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for whichclick.is was fetched 2026-11-09T03:05:13.015Z.

Trust status Neutral

whichclick.is is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.