Referral Rock MCP by usefulapi
REMOTE · REFERRAL-ROCK.USEFULAPI.IO
Read Referral Rock programs, members, referrals, rewards and payouts; add members and referrals.
Available components
Last scanned (3 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
Category CRM and Sales
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 Security78
- 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 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
- 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 & 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 Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2893 tokens (~192/item across 15 items; 15 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 Management3
- Stability observed for 1 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
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.
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 1.1.3 functional
- 24 Oct 26 61
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 25 Oct 2026 · Probed https://referral-rock.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 referral-rock.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 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 | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://referral-rock.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://referral-rock.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://referral-rock.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://referral-rock.usefulapi.io/mcp |
| Authorisation server | https://referral-rock.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://referral-rock.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/referral-rock/ |
| http (plaintext) | http://referral-rock.usefulapi.io/mcp | Inconclusive | 302 | http://referral-rock.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 →
referralrock_create_member Add a member to a program ~242
WRITE: creates a new member (advocate) in a referral program and returns the member with their referral code and share URL. Not idempotent: a repeat call may create a duplicate or fail. When send_confirmation_email is true Referral Rock emails the member the program's confirmation email, which is a message to a real person; the default is false. POST /api/members.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true when send_confirmation_email is true: confirms an email goes to the member. |
| string | yes | Member email address. | |
| external_id | string | – | Your own id for this member, to link it to another system. |
| first_name | string | yes | Member first name. |
| last_name | string | – | Member last name. |
| phone | string | – | Member phone number. |
| program_id | string | yes | Program id to add the member to (see referralrock_list_programs). |
| referral_code | string | – | A custom referral code; Referral Rock generates one when left out. |
| send_confirmation_email | boolean | – | Email the member the program's confirmation email (default false; needs confirm: true). |
No output schema declared.
No examples provided.
referralrock_create_referral Add a referral ~284
WRITE: adds a referral (a lead) to the program of the member who owns the given referral code, as if the lead had used that member's link. A status of qualified or approved can trigger the program's configured rewards for the member, which is a financial commitment, so leave status out (new referrals start as pending) unless you mean it. Not idempotent. POST /api/referrals.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Order amount / total tied to the referral. |
| company_name | string | – | Company name. |
| confirm | boolean | – | Must be true when status is qualified or approved: confirms rewards may be issued. |
| string | – | Referral email address. | |
| external_id | string | – | Your own unique id for the referral (an order or customer id), to find it again. |
| first_name | string | – | Referral first name. |
| last_name | string | – | Referral last name. |
| note | string | – | Private note tied to the referral. |
| phone | string | – | Referral phone number. |
| preferred_contact | string | – | Preferred way to contact the referral. |
| referral_code | string | yes | The referral code of the member who introduced the referral (see referralrock_list_members). |
| status | string | – | Initial status (default pending). qualified / approved may trigger rewards and need confirm: true. |
No output schema declared.
No examples provided.
referralrock_get_member_stats Get member statistics ~104
Sharing, referral and reward statistics of one member over a time period: views, shares, referrals (pending / qualified / approved), reward amounts pending and issued, last share and activity dates. GET /api/memberstats/getsingle.
| Name | Type | Req | Description |
|---|---|---|---|
| member | string | yes | The member's email address, id, external id or referral code. |
| time_period | string | – | All (default), MonthToDate, LastMonth, Last7Days or Last30Days. |
No output schema declared.
No examples provided.
referralrock_get_program Get referral program by name ~54
One referral program by its exact name: id, active flag, offers and URLs. GET /api/program/getsingle.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The program's exact name (see referralrock_list_programs). |
No output schema declared.
No examples provided.
referralrock_get_referral Get referral ~87
One referral by id, email address or external id (at least one is required): status, amount, referring member, notes, custom fields and dates. GET /api/referral/single.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The referral's email address. | |
| external_id | string | – | The referral's external identifier. |
| referral_id | string | – | The referral's id. |
No output schema declared.
No examples provided.
referralrock_list_members List members (advocates) ~226
List members (the people who refer others), newest first by default, with their referral code and share URL, referral counts, rewards earned and activity dates. Filter by program, by an email / id / external id / referral code, by created date, or active vs disabled. GET /api/members.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Results per page, 1-200 (default 20). |
| date_from | string | – | Only members created after this date (yyyy-mm-dd). |
| date_to | string | – | Only members created before this date (yyyy-mm-dd). |
| offset | integer | – | Starting index, 0 based (default 0). Pass the previous reply's next_offset. |
| program | string | – | Program id, program name or program title. |
| query | string | – | A member's email address, id, external id or referral code. |
| show_disabled | boolean | – | true = disabled members, false = active members. Leave out for the default. |
| sort | string | – | Sort order (default Create_Dt_Desc). |
No output schema declared.
No examples provided.
referralrock_list_payout_transactions List payout transactions ~92
Payout transactions already transferred to program participants (type, amount, date, status, destination, vendor errors) and the balance left in the account to cover pending payouts. Optionally for one recipient or one transaction. GET /api/payouts/transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| recipient_id | string | – | Only the transactions paid to this recipient id. |
| transaction_id | string | – | Only this transaction id. |
No output schema declared.
No examples provided.
referralrock_list_pending_payouts List pending payouts ~103
Payouts that are owed but not yet transferred: recipient, program, number of rewards and total amount. Optionally for one recipient, and optionally including rewards whose eligibility date is still in the future. GET /api/payouts/pending.
| Name | Type | Req | Description |
|---|---|---|---|
| include_ineligible | boolean | – | Also include payouts for rewards with an eligibility date in the future (default false). |
| recipient_id | string | – | Only the payouts owed to this recipient id. |
No output schema declared.
No examples provided.
referralrock_list_programs List referral programs ~123
List the referral programs in the account: id, name, type (Web or Form), active flag, title, the member and referral offers and the share/widget URLs. Use the ids (or names) to filter members, referrals and rewards. GET /api/programs.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Results per page, 1-200 (default 20). |
| offset | integer | – | Starting index, 0 based (default 0). Pass the previous reply's next_offset. |
| program | string | – | Only the program with this id. |
No output schema declared.
No examples provided.
referralrock_list_referrals List referrals (leads) ~225
List referrals (the people members referred), newest first by default, with status (pending, qualified, approved, denied), amount, the referring member, notes and dates. Filter by program, status, referring member, free-text query or created date. GET /api/referrals.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Results per page, 1-200 (default 20). |
| date_from | string | – | Only referrals created after this date (yyyy-mm-dd). |
| date_to | string | – | Only referrals created before this date (yyyy-mm-dd). |
| member_id | string | – | Only referrals made by this member id. |
| offset | integer | – | Starting index, 0 based (default 0). Pass the previous reply's next_offset. |
| program | string | – | Program id, program name or program title. |
| query | string | – | A referral's email address, id, external id or referral code. |
| sort | string | – | Sort order (default Create_Dt_Desc). |
| status | string | – | Only referrals in this status. |
No output schema declared.
No examples provided.
referralrock_list_reward_rules List program reward rules ~78
The reward rules of one program: what triggers a reward (referral status, referral count or sales limits), how the amount is worked out (fixed or percent), the payout type and delivery delay. GET /api/rewardrules.
| Name | Type | Req | Description |
|---|---|---|---|
| program_id | string | yes | Program id (a GUID; see referralrock_list_programs). |
No output schema declared.
No examples provided.
referralrock_list_rewards List rewards ~224
List rewards, newest first by default: recipient, amount, status (Pending, Processing, Issued), payout type, eligibility and issue dates, the member and referral behind it. Filter by program, member, status, recipient query or created date. GET /api/rewards.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Results per page, 1-200 (default 20). |
| date_from | string | – | Only rewards created after this date (yyyy-mm-dd). |
| date_to | string | – | Only rewards created before this date (yyyy-mm-dd). |
| member_id | string | – | Only rewards of this member id. |
| offset | integer | – | Starting index, 0 based (default 0). Pass the previous reply's next_offset. |
| program | string | – | Program id, program name or program title. |
| query | string | – | The recipient's email address, id, external id or member referral code. |
| sort | string | – | Sort order (default Create_Dt_Desc). |
| status | string | – | Only rewards in this status. |
No output schema declared.
No examples provided.
referralrock_record_customer Record a customer purchase ~240
WRITE: reports a paying customer to Referral Rock. A customer whose email matches a pending referral turns that referral to approved, which triggers the program's configured rewards for the referring member (a financial commitment that may be paid out automatically). A customer with no matching referral is added as a pre-loaded member to every program that has Preload New Customers on. Returns the outcome per customer (ReferralApproved, MemberPreloaded, Skipped…). Not idempotent. POST /api/customerfeed.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Purchase amount; feeds percentage rewards (default 0). |
| confirm | boolean | yes | Must be true: confirms a matching pending referral may be approved and its rewards issued. |
| string | yes | The customer's email address; the match key against pending referrals and members. | |
| external_id | string | – | Your own id for this customer (for example a CRM id). |
| first_name | string | – | Customer first name. |
| last_name | string | – | Customer last name. |
| phone | string | – | Customer phone number. |
| purchase_date | string | – | Purchase date, ISO 8601 (default: now, UTC). |
No output schema declared.
No examples provided.
referralrock_update_member Update a member ~277
WRITE: changes contact details of an existing member, or disables / re-enables the member (a disabled member can no longer take part in the programs). Only the fields you pass are changed. The member is found by id, referral code, or email / external id plus program_id or program_name; Referral Rock updates it only when it is uniquely identified. POST /api/members/update.
| Name | Type | Req | Description |
|---|---|---|---|
| disabled | boolean | – | true disables the member, false re-enables. |
| string | – | The member's current email address (needs program_id or program_name). | |
| external_id | string | – | The member's current external identifier (needs program_id or program_name). |
| member_id | string | – | The member's id (preferred). |
| new_email | string | – | New email address. |
| new_external_id | string | – | New external identifier. |
| new_first_name | string | – | New first name. |
| new_last_name | string | – | New last name. |
| new_phone | string | – | New phone number. |
| program_id | string | – | Program id; needed together with email or external_id (or give program_name). |
| program_name | string | – | Program name; needed together with email or external_id (or give program_id). |
| referral_code | string | – | The member's referral code. |
No output schema declared.
No examples provided.
referralrock_update_referral Update a referral (status, amount, notes) ~275
WRITE: changes the status, amount or notes of an existing referral. Moving a referral to qualified or approved can trigger the program's configured rewards for the referring member (a financial commitment that may be paid out automatically), and denied stops them: confirm with the user first. Only the fields you pass are changed. The referral is found by id, or by external id / email plus program_id or program_name. POST /api/referral/update.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | New order amount / total (used for percentage rewards). |
| confirm | boolean | – | Must be true when status is qualified or approved, or amount is set: confirms rewards may be issued or changed. |
| string | – | The referral's email address (needs program_id or program_name). | |
| external_id | string | – | The referral's external identifier (needs program_id or program_name). |
| note | string | – | New private note. |
| program_id | string | – | Program id; needed together with external_id or email (or give program_name). |
| program_name | string | – | Program name; needed together with external_id or email (or give program_id). |
| public_note | string | – | New public note. |
| referral_id | string | – | The referral's id (preferred). |
| status | string | – | New status. |
No output schema declared.
No examples provided.
How do I install the Referral Rock MCP by usefulapi server?
Referral Rock MCP by usefulapi is a hosted endpoint at https://referral-rock.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 · referral-rock.usefulapi.io
claude mcp add --transport http io-usefulapi-referral-rock 'https://referral-rock.usefulapi.io/mcp'
What is the Referral Rock MCP by usefulapi server?
Referral Rock MCP by usefulapi is listed in the public MCP registry as io.usefulapi/referral-rock. Read Referral Rock programs, members, referrals, rewards and payouts; add members and referrals. This page covers its hosted endpoint (https://referral-rock.usefulapi.io/mcp).
Is the Referral Rock MCP by usefulapi server safe to use?
Referral Rock MCP by usefulapi scores 62 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 Referral Rock MCP by usefulapi server expose?
Referral Rock MCP by usefulapi exposes 15 tools: referralrock_list_programs, referralrock_get_program, referralrock_list_reward_rules, referralrock_list_members, referralrock_get_member_stats, and 10 more. Their descriptions and schemas cost roughly 2,634 tokens of context every time the server is loaded.
Does the Referral Rock MCP by usefulapi server require authentication?
Yes. Referral Rock MCP by usefulapi 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 Referral Rock MCP by usefulapi server still maintained?
Referral Rock MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.