Daisycon (MCP server)
REMOTE · MCP.DAISYCON.COM · 3 COMPONENTS
Search Daisycon affiliate programs, manage campaigns and leads, and track earnings and statistics.
Available components
Last scanned (10 hours ago)
Scores higher than 13% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: the endpoint responded but didn't complete an MCP handshake over streamable-http. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 22 Oct 26 −54
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.63 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Oct 26 +2
- Schema quality: good → excellent functional
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 5 Nov 2026 · Probed https://mcp.daisycon.com/campaigns/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=daisycon.com | CN=WE1,O=Google Trust Services,C=US | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b740845157e6245135d43e09b8afb57 |
| SANs: daisycon.com, *.daisycon.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.daisycon.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| daisycon.com. | present | 2371 | 13 | Verified |
| mcp.daisycon.com. | Verified address RRset verified with the apex keys |
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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.daisycon.com/campaigns/mcp | Not MCP | 200 | |
| http (plaintext) | http://mcp.daisycon.com/campaigns/mcp | HTTPS enforced | 301 | https://mcp.daisycon.com/campaigns/mcp |
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 →
getAllPublicPrograms ~616
Get all public programs
| Name | Type | Req | Description |
|---|---|---|---|
| advertiser_id | string | – | Filter by advertiser ID(s) |
| allowed_media_type_id | string | – | Filter by allowed media type ID(s) |
| category_id | string | – | Filter by category ID(s) |
| commission_cpc | string | – | 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}) |
| commission_fixed | string | – | 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 | string | – | 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}) |
| currency_code | string | – | Filter by currency code(s) |
| cursor | string | – | Pagination cursor from a previous response. Omit to start from the first page. |
| deeplink | string | – | Filter by deep linking flag (true/false) |
| fields | – | – | The fields to include in each result: a list of names, or a comma-separated string as a fallback. Omit to receive every field. |
| id | string | – | Filter by program ID(s) |
| limit | integer | – | 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. |
| locale_id | string | – | Filter by locale ID(s) |
| order_by | string | – | Field to sort by (id, advertiser_id, name, currency_code, start_date) |
| order_direction | string | – | Sort direction (ASC or DESC) |
| productfeed | string | – | Filter by productfeed flag (true/false) |
| search_term | string | – | Search by program name (partial match) or by program ID (exact match on a term of digits only) |
| similar_to_id | string | – | 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 t… |
| start_date | string | – | 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"}) |
| supply_locale_id | string | – | Filter by supply locale ID(s) |
| type | string | – | Filter by advertiser type(s) (affiliatemarketing/leadgeneration) |
No output schema declared.
No examples provided.
list ~15
List all available tools grouped by category.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Daisycon (MCP server) server?
Daisycon (MCP server) is a hosted endpoint at https://mcp.daisycon.com/campaigns/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 · mcp.daisycon.com
claude mcp add --transport http com-daisycon-mcp-daisycon 'https://mcp.daisycon.com/campaigns/mcp'
What is the Daisycon (MCP server) server?
Daisycon (MCP server) is listed in the public MCP registry as com.daisycon.mcp/daisycon. Search Daisycon affiliate programs, manage campaigns and leads, and track earnings and statistics. This page covers its hosted endpoint (https://mcp.daisycon.com/campaigns/mcp).
Is the Daisycon (MCP server) server safe to use?
Daisycon (MCP server) scores 26 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 Daisycon (MCP server) server expose?
Daisycon (MCP server) exposes 2 tools: getAllPublicPrograms, list. Their descriptions and schemas cost roughly 631 tokens of context every time the server is loaded.
Does the Daisycon (MCP server) server require authentication?
No. We connected to Daisycon (MCP server) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Daisycon (MCP server) server still maintained?
Daisycon (MCP server) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.