affterms — affiliate program terms
REMOTE · AFFILIATEPROGRAMTERMS.COM
Sourced, dated affiliate program terms, read off each company's page: commission, cookie, payout.
Available components
Last scanned (16 hours ago)
Scores higher than 84% 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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1218 tokens (~174/item across 7 items; 7 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 Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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 →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 2026-10-29 → 2026-11-03 functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 31 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.
- 30 Oct 26 0
- Server version: 2026-10-28 → 2026-10-29 functional
- 29 Oct 26 +1
- Server version: 2026-10-27 → 2026-10-28 functional
- 28 Oct 26 0
- Tool “check_ad” was removed ▼ security
- Tool “list_ad_slots” was removed ▼ security
- Tool “submit_ad” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_program” rewrote its description, which is the text the model reads security
- Tool “list_categories” rewrote its description, which is the text the model reads security
- Server version: 2026-10-26 → 2026-10-27 functional
- New tool “featured_availability” functional
- New tool “featured_check_booking” functional
- New tool “featured_prepare_card” functional
- 27 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 2026-10-24 → 2026-10-26 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://affiliateprogramterms.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=affiliateprogramterms.com | CN=WE1,O=Google Trust Services,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | bbe94eff48eeeacf139e75454fdcc11e |
| SANs: affiliateprogramterms.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 insecure
Validation of affiliateprogramterms.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| affiliateprogramterms.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://affiliateprogramterms.com/mcp | Verified | 200 | |
| http (plaintext) | http://affiliateprogramterms.com/mcp | HTTPS enforced | 301 | https://affiliateprogramterms.com/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 →
featured_availability See featured spots by category ~143
Featured placements on affiliateprogramterms.com: a company's affiliate program shown at the top of its category page and under its category on the home page, labelled "Featured", 7d: 7 days for $27, 30d: 30 days for $72, 5 per category, never renewing. Returns, per category, how many spots are open and when the next opens. Use when someone wants to promote their affiliate program to people comparing programs, or asks what featuring costs. Listing itself is free and never sold; featuring changes no figure and no order.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | A category, e.g. "seo" or "hosting". |
No output schema declared.
No examples provided.
featured_check_booking Check a featured booking ~73
Check a featured booking by the id given after payment (FT- followed by 6 letters and digits): whether it is scheduled, active, expired or removed, its category, and when it starts and ends.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The booking id, e.g. FT-7K2Q9X. |
No output schema declared.
No examples provided.
featured_prepare_card Prepare a featured card ~197
Prepare a featured placement for a company's own affiliate program. Give the program's page; returns whether the program is listed (and in which category: featuring is only in that one), the likeliest category from the company's website if it is not listed (pass category to choose another), a draft card from the company's website (name up to 32 characters, one line up to 90, no figures and no web addresses), and a link where the person checks it and pays. Nothing is booked or charged until they pay there. Never pay, and never enter payment details: pass the link to the person.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | A category, e.g. "seo" or "hosting". |
| plan | string | – | 7d: 7 days for $27, 30d: 30 days for $72. |
| program_url | string | yes | The company's own affiliate, referral or partner program page. |
No output schema declared.
No examples provided.
get_program Get one program's terms ~141
Get one tool's affiliate, referral or partner program terms. Use when someone asks about a specific program: "what does beehiiv's affiliate program pay", "does Hunter pay recurring commission", "how long is Hostinger's affiliate cookie", "what is Zyte's minimum payout". `status` is "listed" (commission, recurring or one-time, cookie window, minimum payout, payout method, network and notes, with the vendor page each figure was read from and the date) or "absent" (not listed: offer to submit it with submit_program, if the person agrees).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The product or program name. |
No output schema declared.
No examples provided.
list_categories List categories ~27
The categories in the directory, with how many programs each holds and the page that lists them.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_programs Search affiliate program terms ~203
Look up affiliate, referral and partner program terms. Use when someone asks which companies or tools have an affiliate program, which pay recurring commission, which have the longest cookie window or lowest payout minimum, or wants to compare affiliate programs in a category such as hosting, email or CRM. Returns commission, recurring or one-time, cookie window, minimum payout, payout method and network, each with the vendor page it was read from and the date it was read.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | A category, e.g. "hosting" or "email". |
| limit | integer | – | – |
| min_cookie_days | integer | – | Only programs whose cookie window is at least this many days (or never expires). |
| query | string | – | Words in the program or category name, e.g. "supabase" or "email". Leave out to search everything. |
| recurring | boolean | – | true: only programs that pay on renewals. false: only one-time. |
No output schema declared.
No examples provided.
submit_program Submit a program to the directory ~193
Submit an affiliate, referral or partner program's page to be checked and added to the directory, free. Use only when the person asks for it or agrees, typically after get_program says a program is absent. Send the URL of the vendor's own program page; a person reads the terms off that page, and anything sent as figures is only checked against it, never published. Sending the same URL again returns what happened to it. An email address, only if the person gives one, is used to tell them the outcome.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The person's email, only if they want to hear the outcome. Ask first. | |
| name | string | – | The product name. |
| notes | string | – | Anything already known about the terms. Checked against the page, never published. |
| url | string | yes | The vendor's own affiliate program page, e.g. https://example.com/affiliates. |
No output schema declared.
No examples provided.
How do I install the affterms — affiliate program terms MCP server?
affterms — affiliate program terms is a hosted endpoint at https://affiliateprogramterms.com/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 · affiliateprogramterms.com
claude mcp add --transport http com-affiliateprogramterms-affterms 'https://affiliateprogramterms.com/mcp'
What is the affterms — affiliate program terms MCP server?
affterms — affiliate program terms is an MCP server listed in the public MCP registry as com.affiliateprogramterms/affterms. Sourced, dated affiliate program terms, read off each company's page: commission, cookie, payout. This page covers its hosted endpoint (https://affiliateprogramterms.com/mcp).
Is the affterms — affiliate program terms MCP server safe to use?
affterms — affiliate program terms scores 81 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 affterms — affiliate program terms MCP server expose?
affterms — affiliate program terms exposes 7 tools: search_programs, get_program, list_categories, submit_program, featured_availability, and 2 more. Their descriptions and schemas cost roughly 977 tokens of context every time the server is loaded.
Does the affterms — affiliate program terms MCP server require authentication?
No. We connected to affterms — affiliate program terms without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the affterms — affiliate program terms MCP server still maintained?
affterms — affiliate program terms 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.
What did VerifyMCP test on the affterms — affiliate program terms MCP server?
VerifyMCP ran 13 checks on affterms — affiliate program terms, 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.