io.usefulapi/rewardful
REMOTE · REWARDFUL.USEFULAPI.IO · SCANNED OCT 3
Browse affiliates, referrals, commissions and payouts, and set up campaigns and affiliates.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2507 tokens (~125/item across 20 items; 20 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/rewardful MCP server?
io.usefulapi/rewardful 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'
{
"mcpServers": {
"io-usefulapi-rewardful": {
"url": "https://rewardful.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-rewardful": {
"type": "http",
"url": "https://rewardful.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-rewardful] url = "https://rewardful.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-rewardful": {
"type": "remote",
"url": "https://rewardful.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-rewardful --url 'https://rewardful.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-rewardful:
url: "https://rewardful.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-rewardful": {
"Transport": "http",
"Url": "https://rewardful.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-rewardful -t streamable-http -u 'https://rewardful.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-rewardful": {
"type": "http",
"url": "https://rewardful.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Oct 26 +1
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +53
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 29 Sept 26 18
First indexed and scored.
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 3 Oct 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 | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| 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. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://rewardful.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://rewardful.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://rewardful.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://rewardful.usefulapi.io/mcp |
| Authorisation server | https://rewardful.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://rewardful.usefulapi.io/mcp | HTTPS enforced | 301 | https://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.
What is the io.usefulapi/rewardful MCP server?
io.usefulapi/rewardful is an MCP server 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 io.usefulapi/rewardful MCP server safe to use?
io.usefulapi/rewardful scores 77 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 io.usefulapi/rewardful MCP server expose?
io.usefulapi/rewardful 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 io.usefulapi/rewardful MCP server require authentication?
Yes. io.usefulapi/rewardful asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/rewardful MCP server still maintained?
io.usefulapi/rewardful is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.