Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Clickwise Affiliate Network

REMOTE · PARTNERS.CLICKWISE.NET

Affiliate programs, deals, tracked links and product search, plus merchant program setup tools.

0 this week 74 Trust /100

Last scanned (21 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4484 tokens (~144/item across 31 items; 31 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 31 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 32 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Tool “request_tracked_links” rewrote its description, which is the text the model reads security
    • Tool “request_merchant_onboarding” rewrote its description, which is the text the model reads security
    • Tool “get_monetization_feed” rewrote its description, which is the text the model reads security
    • Tool “create_program” rewrote its description, which is the text the model reads security
  • 19 Nov 26 0
    • Tool “get_payment_status” rewrote its description, which is the text the model reads security
  • 13 Nov 26 0
    • “search_products” reworded the description of “country” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Server version: 1.6.0 → 1.8.0 functional
    • New tool “check_store” functional
    • New tool “list_my_weekly_deals” functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Oct 26 0
    • Stability: 0.97 → pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_products” rewrote its description, which is the text the model reads security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://partners.clickwise.net/api/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=partners.clickwise.net CN=WR3,O=Google Trust Services,C=US 30 Sept 2026 29 Dec 2026 RSA 2048 SHA256-RSA 331ca6cea2d62b851235c8840cba12da
SANs: partners.clickwise.net
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of partners.clickwise.net. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
net. DS published 37331 13 Verified
clickwise.net. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options DENY
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://partners.clickwise.net/api/v1/mcp Verified 200
http (plaintext) http://partners.clickwise.net/api/v1/mcp HTTPS enforced 301 https://partners.clickwise.net:443/api/v1/mcp
MCP tools · 31 exposed · ~4,186 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
answer_program_question ~132

Answer the application question. An agent calls this at a person's request.

NameTypeReqDescription
access_secretstringyes–
application_idintegeryes–
channel_restrictionsarray–Promotion channels prohibited by the merchant for all publishers. An explicit empty list declares no additional prohibitions.
langstring––
messagestring––
terms_acceptedboolean–True only when the person has read the Clickwise merchant terms and told the agent they accept them. The agent never accepts on its own. Send it with terms_version.
terms_versionstring––

No output schema declared.

No examples provided.

apply_to_program ~92

Ask to join a program (program_id from list_my_programs with include_available, or a campaign_id). Clickwise reviews the fit; the result is approved or pending. Requires your own Clickwise affiliate API key on the MCP connection (X-API-Key header or Authorization: Bearer); acts only on your account.

NameTypeReqDescription
campaign_idstring|integer––
program_idinteger––

No output schema declared.

No examples provided.

check_store ~61

Check a store domain against the Clickwise catalog. Returns up to five available programs, absent, or a neutral result. Requires an affiliate OAuth connection with affiliate:read. Send a domain only, without a URL or browsing history.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

create_program ~359

Create a program for its first payment. An agent calls this at a person's request. Default commission 25%, percent range 10–50%; recurring_months: 0 only. No setup fee; you pay on approved sales. The agent never accepts the Clickwise merchant terms on its own: send terms_accepted with terms_version only after the person has read the merchant terms page and told you they accept them. Otherwise leave it out: the program is not set up until the person accepts them and you send terms_accepted with terms_version, here or later in POST /api/v1/onboarding/merchant/{application_id}/ with the access_secret (required action confirm_terms). Clickwise processes the email and other details sent with this tool as described in its privacy notice: https://partners.clickwise.net/en/privacy/.

NameTypeReqDescription
channel_restrictionsarray–Promotion channels prohibited by the merchant for all publishers. An explicit empty list declares no additional prohibitions.
commissionobject––
company_namestring––
contact_emailstring––
cookie_daysinteger––
countrystring––
langstring––
messagestring––
networks_usedarray––
payment_providerstring––
pricing_modelstring––
privacy_policy_urlstring––
product_typestring––
terms_acceptedboolean–True only when the person has read the Clickwise merchant terms and told the agent they accept them. The agent never accepts on its own. Send it with terms_version.
terms_versionstring––
verticalstring––
websitestring––

No output schema declared.

No examples provided.

create_tracking_links ~122

Use this when you already have a Clickwise affiliate API key and want tracking links for programs you are approved in: one per item (the same program and subid return the same link), optionally deep-linking to a landing_url on the merchant's site. Each item reports its own status; a failed item never blocks the others. Without an account use request_tracked_links. Requires your own Clickwise affiliate API key on the MCP connection (X-API-Key header or Authorization: Bearer); acts only on your account.

NameTypeReqDescription
linksarrayyes–

No output schema declared.

No examples provided.

find_affiliate_programs ~276

Use this first when someone without a Clickwise account asks which merchants to promote: it ranks live programs by fit for a described site, app, newsletter or social channel. Does not require signup. For the whole catalogue page by page use list_programs; for the programs your API key is already approved in use list_my_programs.

NameTypeReqDescription
categorystring–Preferred vertical/category.
channelstring–Publishing channel: site, app, newsletter, Instagram, TikTok, coupon, cashback, etc.
countrystring–Main audience country, ISO 3166-1 alpha-2 if known.
include_unreadyboolean–Also return published matched programs whose links are not available yet; can_issue_link_now indicates availability.
limitinteger––
merchantstring–Optional merchant name/domain filter.
networkstring–Optional source network slug; applies only to signed-in affiliates.
publisher_urlstring–Where the affiliate will publish: URL, app URL, social profile, newsletter page, etc.
topicstring–Audience or content topic, e.g. travel deals, AI shopping assistant, sneakers.
traffic_dailyinteger–Estimated daily visits/reach.
traffic_monthlyinteger–Estimated monthly visits/reach.

No output schema declared.

No examples provided.

get_catalog_stats ~60

Public GTIN catalog counts as of generated_at, using the same stored snapshot as /api/v1/public/catalog-stats/. Fixed one-hour validity; snapshot_stale marks older counts, served for up to 7 days. No affiliate data or amounts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_click_report ~139

Your own native Clickwise redirect clicks for an inclusive date range. Returns individual clicks and total, excluding bots by default; upstream network clicks are not included. The REST resource has no grouping. Requires your own Clickwise affiliate API key on the MCP connection (X-API-Key header or Authorization: Bearer); acts only on your account.

NameTypeReqDescription
campaign_idstring––
date_fromstring–YYYY-MM-DD
date_tostring–YYYY-MM-DD
deeplink_idstring––
pageinteger––
page_sizeinteger––
sub_idstring––

No output schema declared.

No examples provided.

get_conversions_key ~45

Reveal a new conversions key once, or rotate with rotate=true. An agent calls this at a person's request. Merchant Bearer token required.

NameTypeReqDescription
rotateboolean––

No output schema declared.

No examples provided.

get_deal ~54

Fetch the full record for a single deal by its slug. Returns title, description, code, discount, target_url, etc., in the requested language.

NameTypeReqDescription
langstring––
slugstringyes–

No output schema declared.

No examples provided.

get_integration_status ~27

Read authenticated test-sale evidence and the last real sale. Merchant Bearer token required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_merchant_credentials ~69

get_merchant_credentials: Returns a merchant API token only if the account has none yet. If one exists, it answers 409 and explains where the account holder can copy it. It never reveals an existing token.

NameTypeReqDescription
access_secretstringyes–
application_idintegeryes–

No output schema declared.

No examples provided.

get_monetization_feed ~257

Use this when a publisher without an account wants links ready to render on a site or app: it creates a provisional Clickwise affiliate and tracked links, as request_tracked_links does, and also returns cards, an HTML embed snippet and a JSON feed. Email is optional; the account is claimed later for payout. For plain links use request_tracked_links; with an existing API key use create_tracking_links. Clickwise processes the email and other details sent with this tool as described in its privacy notice: https://partners.clickwise.net/en/privacy/.

NameTypeReqDescription
categorystring–Preferred vertical/category.
claim_emailstring–Optional email to claim the account (and payout) later.
countrystring–Main audience country, ISO 3166-1 alpha-2.
limitinteger–How many cards to return.
program_idsarray–Optional specific program IDs; omit to let Clickwise pick fitting merchants.
publisher_urlstring–The app/site/profile where the feed will be embedded.
sub_idstring–Optional placement/sub ID for attribution.
topicstring–Audience/content topic, e.g. travel deals, AI shopping assistant, sneakers.

No output schema declared.

No examples provided.

get_news ~35

Fetch the full record for a single news article by its slug.

NameTypeReqDescription
langstring––
slugstringyes–

No output schema declared.

No examples provided.

get_payment_status ~136

Use this when an affiliate asks when they get paid: approved commission not yet paid (per currency and in USD), commission still pending review, the next payment as an estimate with its threshold, the payment method as its type (a bank account shows only its last 4 digits) and, for links in verification, the account's progress towards verification (clicks, networks and days it still needs). Read-only; never returns account numbers, PayPal addresses, postal or tax data. Requires your own Clickwise affiliate API key on the MCP connection (X-API-Key header or Authorization: Bearer); acts only on your account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_performance_report ~132

Your conversions and commission (what you earn), grouped by day, week, month, subid, campaign or status, for up to 366 days (default: last 30). Daily/weekly/monthly series include empty periods. Requires your own Clickwise affiliate API key on the MCP connection (X-API-Key header or Authorization: Bearer); acts only on your account.

NameTypeReqDescription
date_fromstring–YYYY-MM-DD
date_tostring–YYYY-MM-DD
group_bystring––
statusstring––
subidstring––

No output schema declared.

No examples provided.

get_product_feed ~96

Create or refresh a GTIN product feed for your authenticated affiliate and one country, and return its signed URL (json, csv, tsv or xml) with Clickwise /dl/ tracked product links. The same request returns the same URL. Requires your affiliate API key. Current freshness, permissions, assignments and delivery caps apply.

NameTypeReqDescription
categorystring––
countrystringyes–
formatstring––

No output schema declared.

No examples provided.

get_program_status ~38

Read the application and pending question using application_id and access_secret.

NameTypeReqDescription
access_secretstringyes–
application_idintegeryes–

No output schema declared.

No examples provided.

get_results ~49

Read native direct program clicks, pending, approved and rejected conversions, commission by currency and billing status. Merchant Bearer token required.

NameTypeReqDescription
daysinteger––
group_bystring––

No output schema declared.

No examples provided.

get_tracked_link_request ~47

Fetch a link request, affiliate RefId, review status, and issued links using its access secret.

NameTypeReqDescription
access_secretstringyes–
application_idintegeryes–

No output schema declared.

No examples provided.

get_tracking_link ~47

Issue a nonpayable house probe link, integration steps and a prompt for Lovable, Bolt or v0. An agent calls this at a person's request. Merchant Bearer token required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_conversions ~120

Your individual conversions (default: last 90 days) with status, commission, currency and subid, plus a per-subid rollup. Requires your own Clickwise affiliate API key on the MCP connection (X-API-Key header or Authorization: Bearer); acts only on your account.

NameTypeReqDescription
date_fromstring–YYYY-MM-DD
date_tostring–YYYY-MM-DD
pageinteger––
page_sizeinteger––
statusstring––
subidstring––

No output schema declared.

No examples provided.

list_deals ~111

List active Clickwise deals and offers, optionally filtered by language, category, country or merchant.

NameTypeReqDescription
categorystring–e.g. fashion, travel, electronics, health
countrystring–ISO 3166-1 alpha-2 (US, ES, BR, ...)
langstring––
limitinteger––
merchantstring–Merchant name or domain
networkstring–Optional source network slug; applies only to signed-in affiliates.

No output schema declared.

No examples provided.

list_my_programs ~134

Use this when you hold a Clickwise affiliate API key and need the programs that key is approved to promote, with link readiness and your existing link count; set include_available to add the ones you can apply to. For discovery without an account use find_affiliate_programs or list_programs. Requires your own Clickwise affiliate API key on the MCP connection (X-API-Key header or Authorization: Bearer); acts only on your account.

NameTypeReqDescription
include_availableboolean––
pageinteger––
page_sizeinteger––
searchstring–Merchant/campaign name filter.

No output schema declared.

No examples provided.

list_my_weekly_deals ~58

Read the weekly deals available to your Clickwise affiliate account. Returns existing deal details only; no tracked links are created. Requires affiliate:read on your OAuth connection or your own affiliate API key.

NameTypeReqDescription
langstring––

No output schema declared.

No examples provided.

list_news ~56

List Clickwise news announcements about affiliate programs (policy changes, launches, shutdowns, commission updates).

NameTypeReqDescription
langstring––
limitinteger––
networkstring––
severitystring––

No output schema declared.

No examples provided.

list_programs ~154

Use this to browse the whole live catalogue page by page, filtered by merchant, category or country, when find_affiliate_programs' ranked top matches are not enough. No key needed; it shows programs anyone can join. For the programs your API key is approved in use list_my_programs.

NameTypeReqDescription
categorystring––
countrystring–ISO 3166-1 alpha-2
merchantstring–Merchant name or domain
networkstring–Optional source network slug; applies only to signed-in affiliates.
pageinteger––
page_sizeinteger––
ready_onlyboolean–Only programs that can issue a tracked link right now.

No output schema declared.

No examples provided.

request_merchant_onboarding ~367

Alias of create_program. Create a program for its first payment. An agent calls this at a person's request. Default commission 25%, percent range 10–50%; recurring_months: 0 only. No setup fee; you pay on approved sales. The agent never accepts the Clickwise merchant terms on its own: send terms_accepted with terms_version only after the person has read the merchant terms page and told you they accept them. Otherwise leave it out: the program is not set up until the person accepts them and you send terms_accepted with terms_version, here or later in POST /api/v1/onboarding/merchant/{application_id}/ with the access_secret (required action confirm_terms). Clickwise processes the email and other details sent with this tool as described in its privacy notice: https://partners.clickwise.net/en/privacy/.

NameTypeReqDescription
channel_restrictionsarray–Promotion channels prohibited by the merchant for all publishers. An explicit empty list declares no additional prohibitions.
commissionobject––
company_namestring––
contact_emailstring––
cookie_daysinteger––
countrystring––
langstring––
messagestring––
networks_usedarray––
payment_providerstring––
pricing_modelstring––
privacy_policy_urlstring––
product_typestring––
terms_acceptedboolean–True only when the person has read the Clickwise merchant terms and told the agent they accept them. The agent never accepts on its own. Send it with terms_version.
terms_versionstring––
verticalstring––
websitestring––

No output schema declared.

No examples provided.

request_tracked_links ~263

Use this when you have no Clickwise account yet and want tracked links: it creates a provisional affiliate and returns links for the programs that can issue one to it. Email is optional; the account is claimed and payout details are added later (update_profile). With an API key use create_tracking_links; for ready-made cards and an embed use get_monetization_feed. Clickwise processes the email and other details sent with this tool as described in its privacy notice: https://partners.clickwise.net/en/privacy/.

NameTypeReqDescription
categorystring––
channelstring––
claim_emailstring–Optional email to claim the account later; not required to get links.
countrystring––
limitinteger––
placement_descriptionstring–Short description of how/where links will be used.
program_idsarray–Program IDs returned by find_affiliate_programs. If omitted, Clickwise picks fitting programs.
publisher_urlstring–Where the affiliate will publish. URL/profile/app is strongly recommended.
sub_idstring–Optional placement/sub ID for attribution.
topicstring––
traffic_dailyinteger––
traffic_monthlyinteger––

No output schema declared.

No examples provided.

search_products ~507

Search fresh GTIN products in the catalog your affiliate can deliver (freshness, permissions and caps apply). Requires your affiliate API key in X-API-Key or Bearer authorization; a sandbox key (cw_sbx_, free at partners.clickwise.net/developers) also works; sandbox links are examples and do not track clicks or earn commission. Every key gets exactly the REST GET /api/v1/publisher/products/ format (with gtin: /products/lookup/): products with id, gtin, title, price and currency, url (a Clickwise /dl/ tracked link created for your affiliate the first time a product is returned), image, merchant (id, name and its public website domain), availability, country, brand, category, regular_price, description, size, color and group_id (shared by the sizes of one model and colour), plus count, total and total_exact. Search by text, brand or category, or list one market by country alone; min_price and max_price filter by price in each product's own currency (inclusive, no conversion) and currency keeps one currency; with gtin every market carrying that GTIN is searched; offset paginates. Example: text "smartwatch" with country "DE" returns offers with a publisher key or a sandbox key. Add currency "EUR" to keep only euro prices.

NameTypeReqDescription
brandstring––
categorystring––
countrystring–ISO 3166-1 alpha-2 market code, for example US or GB. Required unless you search by gtin or your account has a market list.
currencystring–ISO 4217 code: only products priced in this currency (the price range then applies to it).
gtinstring––
limitinteger––
max_pricenumber|string–Inclusive upper price bound, in each product's own currency (no conversion). Number from 0 with up to 4 decimals.
min_pricenumber|string–Inclusive lower price bound, in each product's own currency (no conversion). Number from 0 with up to 4 decimals.
offsetinteger––
subidstring–Your own sub-ID for these links (up to 36 characters: letters, digits, _ or -; no personal data). A sale made through one of them reports it in your conversions.
textstring––

No output schema declared.

No examples provided.

update_profile ~143

Update a creator's monetization profile (claim email, display name, website, country, payment method) using the application_id + access_secret returned by request_tracked_links. Overwrites the fields provided. Lets a creator's assistant complete claim/payout details without leaving chat.

NameTypeReqDescription
access_secretstringyes–
application_idintegeryes–
claim_emailstring––
countrystring––
display_namestring––
payment_methodobject–e.g. {"Type": "Paypal", "Paypal_ID": "you@example.com", "Paypal_Name": "Your Name"}
website_urlstring––

No output schema declared.

No examples provided.

Install

How do I install the Clickwise Affiliate Network MCP server?

Clickwise Affiliate Network is a hosted endpoint at https://partners.clickwise.net/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · partners.clickwise.net

# add to Claude Code
claude mcp add --transport http net-clickwise-mcp 'https://partners.clickwise.net/api/v1/mcp'
Common questions

What is the Clickwise Affiliate Network MCP server?

Clickwise Affiliate Network is an MCP server listed in the public MCP registry as net.clickwise/mcp. Affiliate programs, deals, tracked links and product search, plus merchant program setup tools. This page covers its hosted endpoint (https://partners.clickwise.net/api/v1/mcp).

Is the Clickwise Affiliate Network MCP server safe to use?

Clickwise Affiliate Network scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Clickwise Affiliate Network MCP server expose?

Clickwise Affiliate Network exposes 31 tools: search_products, get_product_feed, get_catalog_stats, list_deals, get_deal, and 26 more. Their descriptions and schemas cost roughly 4,186 tokens of context every time the server is loaded.

Does the Clickwise Affiliate Network MCP server require authentication?

No. We connected to Clickwise Affiliate Network without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Clickwise Affiliate Network MCP server still maintained?

Clickwise Affiliate Network is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Clickwise Affiliate Network MCP server?

VerifyMCP ran 13 checks on Clickwise Affiliate Network, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.