Daisycon (MCP server)

Server Details

Search Daisycon affiliate programs, manage campaigns and leads, and track earnings and statistics.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Last Tested: 2026-10-08 06:14
Transport: Streamable HTTP · MCP 2025-11-25
URL

TDQS

B3/5.0

Scored 2026-10-07 19:20 across 2 tools

Disambiguation4/5

getAllPublicPrograms and list have clearly different targets: public programs vs. available MCP tools. However, the bare name 'list' is generic and could momentarily be mistaken for listing domain objects before the description clarifies it.

Naming Consistency3/5

getAllPublicPrograms uses camelCase with a verb-object structure, while 'list' is a bare lowercase verb. The two names are readable but do not follow a consistent naming pattern.

Tool Count3/5

Two tools is thin for a Daisycon integration, especially since one is a meta-tool for tool discovery rather than a domain operation. It is borderline rather than an extreme mismatch.

Completeness2/5

The surface exposes only a way to get all public programs plus a tool-listing helper. It lacks core affiliate-network operations such as program details, filtering/searching, or transaction/report access, creating significant gaps.

Available Tools

2 tools

getAllPublicProgramsC

Read-onlyIdempotent

Inspect

Get all public programs

ParametersJSON Schema

Name	Required	Description
`id`	No	Filter by program ID(s)
`type`	No	Filter by advertiser type(s) (affiliatemarketing/leadgeneration)
`limit`	No	Maximum results per page (1-1000, default 100). Only used when starting a new list (no cursor supplied); once a cursor is used, its own limit applies and this is ignored.
`cursor`	No	Pagination cursor from a previous response. Omit to start from the first page.
`fields`	No	The fields to include in each result: a list of names, or a comma-separated string as a fallback. Omit to receive every field.
`deeplink`	No	Filter by deep linking flag (true/false)
`order_by`	No	Field to sort by (id, advertiser_id, name, currency_code, start_date)
`locale_id`	No	Filter by locale ID(s)
`start_date`	No	Filter on the date a program started, as a date (Y-m-d) or as a range (json: gt, gte, lt, lte, e.g. {"gte":"2024-01-01","lte":"2024-12-31"})
`category_id`	No	Filter by category ID(s)
`productfeed`	No	Filter by productfeed flag (true/false)
`search_term`	No	Search by program name (partial match) or by program ID (exact match on a term of digits only)
`advertiser_id`	No	Filter by advertiser ID(s)
`currency_code`	No	Filter by currency code(s)
`similar_to_id`	No	Return the campaigns that resemble the given campaign ID(s), most similar first. Resemblance is based on the English campaign descriptions. The campaigns asked about are not part of the answer, and this ordering replaces order_by
`commission_cpc`	No	Filter on the cost per click a program pays, in the currency defined by currency_code, as an amount or as a range (json: gt, gte, lt, lte, e.g. {"gte":0.1,"lte":1})
`order_direction`	No	Sort direction (ASC or DESC)
`commission_fixed`	No	Filter on the fixed commission a program pays, in the currency defined by currency_code, as an amount or as a range (json: gt, gte, lt, lte, e.g. {"gte":5,"lte":25})
`commission_ratio`	No	Filter on the commission percentage a program pays, as a percentage or as a range (json: gt, gte, lt, lte, e.g. {"gte":5,"lte":25})
`supply_locale_id`	No	Filter by supply locale ID(s)
`allowed_media_type_id`	No	Filter by allowed media type ID(s)

TDQS

C2.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description itself adds no behavioral context — nothing about pagination, filtering, or result shape beyond what annotations and schema already provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short, front-loaded sentence with no waste, but it is under-specified rather than genuinely concise for a tool this complex. Brevity here reflects a lack of content, not efficient structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 21-parameter listing tool with heavy filtering, cursor pagination, field selection, and no output schema, the description omits any mention of pagination, filtering capability, or relationship to the sibling 'list' tool. It is inadequate for the complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (21 params, all documented with formats, ranges, and defaults), so the schema carries the semantic burden. The description adds nothing to parameter meaning; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('public programs'), so an agent knows the basic operation. However, it offers no differentiation from the sibling tool 'list', and the word 'all' is misleading given the 21 filtering/pagination parameters.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use guidance, no prerequisites, and never mentions the sibling 'list' tool or any alternative. An agent must infer everything about selection from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

listB

Read-onlyIdempotent

Inspect

List all available tools grouped by category.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

B3.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only that results are grouped by category, an output-shape detail; it says nothing about scope, size of result, or what "tools" refers to.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the return-shape hint (grouped by category) is packed into the same sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless read tool with no output schema, safety is covered by annotations, but "tools" is ambiguous (MCP tool registry vs. some domain entity) and the description never states what the response contains beyond grouping. Adequate but leaves a real interpretive gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to clarify — baseline 4 applies. The schema is empty and fully consistent with a no-argument listing call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("List") and resource ("all available tools") plus the grouping behavior, so the agent knows what comes back. It does not differentiate from the sibling getAllPublicPrograms, but that sibling is clearly a different domain, so the risk of confusion is low.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use or when-not-to-use guidance and names no alternative. It merely asserts what the tool returns, leaving the agent to infer that this is the discovery/entry-point call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updateOct 7, 2026

ChangedgetAllPublicPrograms3 fields changed

addedInput schema / properties / fields / anyOf

Added value: +[
+  {
+    "items": {
+      "enum": [
+        "advertiser_id",
+        "id",
+        "name",
+        "currency_code",
+        "type",
+        "start_date",
+        "categories",
+        "locales",
+        "supply_locales",
+        "productfeed",
+        "deeplink",
+        "allowed_media_types",
+        "commission",
+        "links"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "description": "Fallback for comma-separated values, like: 'id,name'",
+    "type": "string"
+  }
+]

changedInput schema / properties / fields / description

Previous value: -"Comma-separated list of fields to include in the response. The data of the fields left out is not fetched"New value: +"The fields to include in each result: a list of names, or a comma-separated string as a fallback. Omit to receive every field."

removedInput schema / properties / fields / type
```
Removed value: -"string"
```

1 tool updateOct 6, 2026

ChangedgetAllPublicPrograms1 field changed

changedInput schema / properties / limit / description

Previous value: -"Maximum results per page (1-1000, default 100). Only used when starting a new list (no cursor supplied) — once a cursor is used, its own limit applies and this is ignored."New value: +"Maximum results per page (1-1000, default 100). Only used when starting a new list (no cursor supplied); once a cursor is used, its own limit applies and this is ignored."

2 tool updatesOct 2, 2026
- First observedgetAllPublicPrograms
- First observedlist

Related MCP Connectors

openaffiliate-mcp A
io.github.sonpiaz
Search and discover affiliate programs with agent-ready data and commission details.
E-commerce & Retail Marketing Search
32
rewardful A
io.usefulapi
Browse affiliates, referrals, commissions and payouts, and set up campaigns and affiliates.
Marketing Payments & Billing CRM
1
directory A
cc.bestaffiliateprograms
Search 4,825 affiliate programs by commission, cookie window and network, with source confidence.
E-commerce & Retail Marketing
51
BacklinkswinkelOAuth
io.github.backlinkswinkel
Search Dutch sites in the Backlinkswinkel catalogue, order backlinks after confirmation, track them.
Marketing Search E-commerce & Retail
1

Related MCP Servers

MCP Affiliate Server
E-commerce & Retail Marketing
Scientia07
A
license
A
quality
D
maintenance
Enables AI assistants to search products and generate affiliate links across European and global affiliate networks, automating product discovery and link creation for monetization.
Updated 8 months ago (2026-02-17 15:03 UTC)
5
MIT
Affilync MCP Server
Marketing E-commerce & Retail App Automation
affilync
F
license
A
quality
C
maintenance
Enables users to manage affiliate marketing directly within Claude by connecting to the Affilync platform. Affiliates can search campaigns and track earnings, while brands can create campaigns, monitor performance, and manage affiliate applications through natural language.
Updated 13 days ago (2026-09-24 19:38 UTC)
20
1
-
CJ MCP Server
E-commerce & Retail Marketing App Automation
finedesignz
F
license
Not graded
quality
Not graded
maintenance
Provides comprehensive access to the Commission Junction affiliate network API for both publishers and advertisers. It enables users to manage affiliate links, track commissions, search for products, and handle order conversions through natural language interfaces.
Updated 7 months ago (2026-03-20 00:29 UTC)
5
-
CBAPI.dev MCP Server
E-commerce & Retail Search
dbansana
F
license
Not graded
quality
D
maintenance
Enables AI agents to search products across affiliate networks, compare commissions, find arbitrage opportunities, and get auto-injected affiliate links via MCP.
Updated 2 months ago (2026-08-07 04:20 UTC)
-