Rewardful MCP by usefulapi
REMOTE · REWARDFUL.USEFULAPI.IO
Browse affiliates, referrals, commissions and payouts, and set up campaigns and affiliates.
Available components
Last scanned (19 hours ago)
Scores higher than 3% of remote servers
Reachable. Last reached 21 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. 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.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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.
- 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
- 1 Nov 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +2
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_or_update_an_affiliate_add_a_link_or_coupon” functional
- New prompt “check_payouts_and_the_commissions_in_them” functional
- New prompt “find_the_commissions_you_still_owe” functional
- New prompt “review_create_or_update_campaign_reward_rules” functional
- New prompt “see_how_your_affiliates_perform” functional
- New prompt “trace_referrals_from_visitor_to_conversion” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 +1
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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://rewardful.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 11 Nov 2026 | 9 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 93e2fea3bbc31354138c8a47c5e87592 |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| 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 rewardful.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rewardful.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/rewardful/ |
| http (plaintext) | http://rewardful.usefulapi.io/mcp | Inconclusive | 302 | http://rewardful.usefulapi.io/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 →
rewardful_create_affiliate Create an affiliate ~231
Add an affiliate (or a customer referrer, by passing stripe_customer_id). Rewardful sends NO welcome email for API-created affiliates. Rewardful: POST /v1/affiliates.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | – | Campaign to put the affiliate in (default campaign if omitted on create). |
| string | yes | Email address. | |
| first_name | string | yes | First name. |
| last_name | string | yes | Last name. |
| paypal_email | string | – | PayPal address commissions should be paid to. |
| receive_new_commission_notifications | boolean | – | Email the affiliate when they earn a commission (default true). |
| state | string | – | Affiliate state. Disabled/suspicious affiliates stop tracking and earning and can't log in. |
| stripe_customer_id | string | – | Customer-referral programs only: the live-mode Stripe customer that receives account credits. |
| token | string | – | Link token, e.g. `jb007` for ?via=jb007. Letters, numbers and dashes only. |
| wise_email | string | – | Wise address commissions should be paid to. |
No output schema declared.
No examples provided.
rewardful_create_affiliate_coupon Create an affiliate coupon ~104
Assign a coupon / promotion code to an affiliate so sales using it are credited to them. The code must match one defined in Stripe, and the affiliate's campaign must have a campaign coupon set in the dashboard. Rewardful: POST /v1/affiliate_coupons.
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_id | string | yes | The affiliate's id (UUID). |
| token | string | yes | The exact coupon / promotion code as defined in Stripe, e.g. MYCODE. |
No output schema declared.
No examples provided.
rewardful_create_affiliate_link Create an affiliate link ~89
Give an affiliate an additional tracking link. A token is generated if omitted. Growth/Enterprise plans only. Rewardful: POST /v1/affiliate_links.
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_id | string | yes | The affiliate's id (UUID). |
| token | string | – | Link token, e.g. `jb007` for ?via=jb007. Letters, numbers and dashes only. |
No output schema declared.
No examples provided.
rewardful_create_campaign Create a campaign ~231
Create a new affiliate campaign with its reward rule. For reward_type percent pass commission_percent; for amount pass commission_amount_cents and commission_amount_currency. Rewardful: POST /v1/campaigns.
| Name | Type | Req | Description |
|---|---|---|---|
| commission_amount_cents | integer | – | Fixed commission in cents. Required when reward_type is amount. |
| commission_amount_currency | string | – | ISO currency code of the fixed commission, e.g. USD. Required when reward_type is amount. |
| commission_percent | number | – | Commission percentage. Required when reward_type is percent. |
| minimum_payout_cents | integer | – | Minimum cumulative commissions before a payout, in cents of the company's display currency. |
| name | string | yes | The campaign's name. |
| private | boolean | – | true = invite-only; false = anyone can sign up. |
| reward_type | string | yes | Percent of each sale, or a fixed amount. |
| stripe_coupon_id | string | – | Stripe coupon for double-sided incentives. Growth/Enterprise plans only. |
| url | string | yes | Base URL used to build affiliate links, e.g. https://example.com. |
No output schema declared.
No examples provided.
rewardful_get_affiliate Get one affiliate ~61
Fetch a single affiliate by id, including their campaign, links, coupon and visitor/lead/conversion counts. Rewardful: GET /v1/affiliates/:id.
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_id | string | yes | The affiliate's id (UUID). |
No output schema declared.
No examples provided.
rewardful_get_affiliate_coupon Get one affiliate coupon ~50
Fetch a single affiliate coupon by id. Rewardful: GET /v1/affiliate_coupons/:id.
| Name | Type | Req | Description |
|---|---|---|---|
| coupon_id | string | yes | The affiliate coupon's id (UUID). |
No output schema declared.
No examples provided.
rewardful_get_affiliate_link Get one affiliate link ~48
Fetch a single affiliate link by id. Rewardful: GET /v1/affiliate_links/:id.
| Name | Type | Req | Description |
|---|---|---|---|
| link_id | string | yes | The affiliate link's id (UUID). |
No output schema declared.
No examples provided.
rewardful_get_campaign Get one campaign ~44
Fetch a single campaign by id. Rewardful: GET /v1/campaigns/:id.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign's id (UUID). |
No output schema declared.
No examples provided.
rewardful_get_commission Get one commission ~69
Fetch a single commission by id, with its campaign and the sale (charge, refund and tax amounts, referral, customer, affiliate) that earned it. Rewardful: GET /v1/commissions/:id.
| Name | Type | Req | Description |
|---|---|---|---|
| commission_id | string | yes | The commission's id (UUID). |
No output schema declared.
No examples provided.
rewardful_get_payout Get one payout ~54
Fetch a single payout by id, with the affiliate and the commissions it bundles. Rewardful: GET /v1/payouts/:id.
| Name | Type | Req | Description |
|---|---|---|---|
| payout_id | string | yes | The payout's id (UUID). |
No output schema declared.
No examples provided.
rewardful_list_affiliate_coupons List affiliate coupons ~100
List affiliate coupon / promotion codes (token, Stripe id, leads, conversions, archived), optionally for one affiliate. Rewardful: GET /v1/affiliate_coupons.
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_id | string | – | Only this affiliate's coupons. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1. See pagination.next_page. |
No output schema declared.
No examples provided.
rewardful_list_affiliate_links List affiliate links ~80
List affiliate links (URL, token, visitors, leads, conversions, affiliate_id), newest first. Rewardful: GET /v1/affiliate_links.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1. See pagination.next_page. |
No output schema declared.
No examples provided.
rewardful_list_affiliates List affiliates ~169
List affiliates, newest first, with visitors/leads/conversions. Filter by campaign, or look one up by email or Stripe customer id (returns zero or one). Expand campaign, links or commission_stats for more detail. Rewardful: GET /v1/affiliates.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | – | Only affiliates in this campaign. |
| string | – | Only the affiliate with this email. | |
| expand | array | – | Nested objects to include for each affiliate. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1. See pagination.next_page. |
| stripe_customer_id | string | – | Only the customer-referrer affiliate tied to this Stripe customer (cus_...). |
No output schema declared.
No examples provided.
rewardful_list_campaigns List campaigns ~93
List the affiliate program's campaigns with their reward rules (percent or fixed commission, payout minimum, referral expiry) and totals (visitors, leads, conversions, affiliates). Rewardful: GET /v1/campaigns.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1. See pagination.next_page. |
No output schema declared.
No examples provided.
rewardful_list_commissions List commissions ~151
List commissions (rewards owed for referred customers' payments) newest first, with amount in cents, currency and state (pending, due, paid, voided). Filter by affiliate or state; expand the sale (with referral, customer and affiliate) or campaign. Rewardful: GET /v1/commissions.
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_id | string | – | Only this affiliate's commissions. |
| expand | array | – | Nested objects to include for each commission. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1. See pagination.next_page. |
| state | array | – | Only commissions in these states. |
No output schema declared.
No examples provided.
rewardful_list_payouts List payouts ~139
List payouts — bundles of an affiliate's payable commissions — newest first, with amount, currency and state (pending, due, processing, paid). Filter by affiliate or state; expand affiliate or commissions. Rewardful: GET /v1/payouts.
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_id | string | – | Only this affiliate's payouts. |
| expand | array | – | Nested objects to include for each payout. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1. See pagination.next_page. |
| state | array | – | Only payouts in these states. |
No output schema declared.
No examples provided.
rewardful_list_referrals List referrals ~216
List referrals — visitors who arrived via an affiliate link — newest first, with their conversion state (visitor, lead, conversion), customer and link. Filter by affiliate, state, email, Stripe customer or an updated-at window. Rewardful: GET /v1/referrals.
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_id | string | – | Only this affiliate's referrals. |
| conversion_state | array | – | Only referrals currently in these conversion states. |
| string | – | Only referrals with this customer email. | |
| expand | array | – | Include the full affiliate object for each referral. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1. See pagination.next_page. |
| stripe_customer_id | string | – | Only referrals with this Stripe customer (cus_...). |
| updated_since | string | – | ISO 8601 timestamp: only referrals updated after it. |
| updated_until | string | – | ISO 8601 timestamp: only referrals updated before it. |
No output schema declared.
No examples provided.
rewardful_update_affiliate Update an affiliate ~227
Change an affiliate's name, email, payout emails, notifications, campaign (moves them) or state. Setting state to disabled stops tracking and earning; set it back to active to undo. Rewardful: PUT /v1/affiliates/:id.
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_id | string | yes | The affiliate's id (UUID). |
| campaign_id | string | – | Campaign to put the affiliate in (default campaign if omitted on create). |
| string | – | Email address. | |
| first_name | string | – | First name. |
| last_name | string | – | Last name. |
| paypal_email | string | – | PayPal address commissions should be paid to. |
| receive_new_commission_notifications | boolean | – | Email the affiliate when they earn a commission (default true). |
| state | string | – | Affiliate state. Disabled/suspicious affiliates stop tracking and earning and can't log in. |
| stripe_customer_id | string | – | Customer-referral programs only: the live-mode Stripe customer that receives account credits. |
| wise_email | string | – | Wise address commissions should be paid to. |
No output schema declared.
No examples provided.
rewardful_update_affiliate_link Change an affiliate link's token ~109
Change the token of an existing affiliate link. WARNING: the old token stops tracking immediately — links already shared with it break. Prefer rewardful_create_affiliate_link to add a second token. Rewardful: PUT /v1/affiliate_links/:id.
| Name | Type | Req | Description |
|---|---|---|---|
| link_id | string | yes | The affiliate link's id (UUID). |
| token | string | yes | Link token, e.g. `jb007` for ?via=jb007. Letters, numbers and dashes only. |
No output schema declared.
No examples provided.
rewardful_update_campaign Update a campaign ~242
Change a campaign's name, URL, visibility, reward rule, payout minimum or coupon. Only the fields you pass change. Rewardful: PUT /v1/campaigns/:id.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign's id (UUID). |
| commission_amount_cents | integer | – | Fixed commission in cents. Required when reward_type is amount. |
| commission_amount_currency | string | – | ISO currency code of the fixed commission, e.g. USD. Required when reward_type is amount. |
| commission_percent | number | – | Commission percentage. Required when reward_type is percent. |
| minimum_payout_cents | integer | – | Minimum cumulative commissions before a payout, in cents of the company's display currency. |
| name | string | – | The campaign's name. |
| private | boolean | – | true = invite-only; false = anyone can sign up. |
| reward_type | string | – | Percent of each sale, or a fixed amount. |
| stripe_coupon_id | string | – | Stripe coupon for double-sided incentives. Growth/Enterprise plans only. |
| url | string | – | Base URL used to build affiliate links, e.g. https://example.com. |
No output schema declared.
No examples provided.
How do I install the Rewardful MCP by usefulapi server?
Rewardful MCP by usefulapi is a hosted endpoint at https://rewardful.usefulapi.io/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 · rewardful.usefulapi.io
claude mcp add --transport http io-usefulapi-rewardful 'https://rewardful.usefulapi.io/mcp'
What is the Rewardful MCP by usefulapi server?
Rewardful MCP by usefulapi is listed in the public MCP registry as io.usefulapi/rewardful. Browse affiliates, referrals, commissions and payouts, and set up campaigns and affiliates. This page covers its hosted endpoint (https://rewardful.usefulapi.io/mcp).
Is the Rewardful MCP by usefulapi server safe to use?
Rewardful MCP by usefulapi scores 18 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 Rewardful MCP by usefulapi server expose?
Rewardful MCP by usefulapi exposes 20 tools: rewardful_list_campaigns, rewardful_get_campaign, rewardful_list_affiliates, rewardful_get_affiliate, rewardful_list_affiliate_links, and 15 more. Their descriptions and schemas cost roughly 2,507 tokens of context every time the server is loaded.
Does the Rewardful MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Rewardful MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Rewardful MCP by usefulapi server still maintained?
Rewardful MCP by usefulapi 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 Rewardful MCP by usefulapi server?
VerifyMCP ran 4 checks on Rewardful MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Rewardful MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.