Skip to content

MCP servers › io.usefulapi › referral-rock

MCP server · registry snapshot 2026-10-24 · last tested 2026-10-24

io.usefulapi/referral-rock

Read Referral Rock programs, members, referrals, rewards and payouts; add members and referrals. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-24version 1.1.0JavaScriptstreamable HTTP15 tools

Summary

io.usefulapi/referral-rock is a remote MCP server listed in the official MCP registry at version 1.1.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 15 tools, 0 resources and 1 prompt.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not checked: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Repository
public
Tools
15
Last tested
2026-10-24

Add to your client

Observed fact

This server accepted a session without any credential and lists 5 tools whose name or declaration suggests they change data (referralrock_create_member, referralrock_update_member, referralrock_create_referral, referralrock_update_referral, referralrock_record_customer). That is our reading of the names; we did not call them. Source: our connection, 2026-10-24.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-24
Mode
read-only (no tool calls)
Latest version
1.1.0, published 2026-10-24 (registry, as of the 2026-10-24 snapshot)
First listed version
2026-10-24 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, all on 2026-10-24; 2 in the 90 days before the 2026-10-24 snapshot.
Most recent 2 versions
  • 1.1.0 · 2026-10-24
  • 1.0.0 · 2026-10-24
(versions still listed in the registry only)
Registry data
snapshot 2026-10-24
Package and repository
checked 2026-10-24
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-23, listed on 2026-10-24 with version 1.1.0 (published 2026-10-24).

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24.

What it is

What does this server offer?

Observed inventory
15tools
0resources
1prompts

None of its 15 tools are described as changing anything. For 15 the reading was uncertain, so no mark is shown.

  • referralrock_list_programs

    “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.”

    Publisher declares: read-only yes · destructive no · open-world yes

    3 inputs
    • programstring“Only the program with this id.”
    • offsetinteger“Starting index, 0 based (default 0).”
    • countinteger“Results per page, 1-200 (default 20).”
  • referralrock_get_program

    “One referral program by its exact name: id, active flag, offers and URLs.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • namestringrequired“The program's exact name (see referralrock_list_programs).”
  • referralrock_list_reward_rules

    “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.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • program_idstringrequired“Program id (a GUID; see referralrock_list_programs).”
  • referralrock_list_members

    “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.”

    Publisher declares: read-only yes · destructive no · open-world yes

    8 inputs
    • programstring“Program id, program name or program title.”
    • querystring“A member's email address, id, external id or referral code.”
    • show_disabledboolean“true = disabled members, false = active members.”
    • sortstring“Sort order (default Create_Dt_Desc).”
    • date_fromstring“Only members created after this date (yyyy-mm-dd).”
    • date_tostring“Only members created before this date (yyyy-mm-dd).”
    • offsetinteger“Starting index, 0 based (default 0).”
    • countinteger“Results per page, 1-200 (default 20).”
  • referralrock_get_member_stats

    “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.”

    Publisher declares: read-only yes · destructive no · open-world yes

    2 inputs, 1 required
    • memberstringrequired“The member's email address, id, external id or referral code.”
    • time_periodstring“All (default), MonthToDate, LastMonth, Last7Days or Last30Days.”
  • referralrock_list_referrals

    “List referrals (the people members referred), newest first by default, with status (pending, qualified, approved, denied), amount, the referring member, notes and dates.”

    Publisher declares: read-only yes · destructive no · open-world yes

    9 inputs
    • programstring“Program id, program name or program title.”
    • statusstring“Only referrals in this status.”
    • member_idstring“Only referrals made by this member id.”
    • querystring“A referral's email address, id, external id or referral code.”
    • sortstring“Sort order (default Create_Dt_Desc).”
    • date_fromstring“Only referrals created after this date (yyyy-mm-dd).”
    • date_tostring“Only referrals created before this date (yyyy-mm-dd).”
    • offsetinteger“Starting index, 0 based (default 0).”
    • countinteger“Results per page, 1-200 (default 20).”
  • referralrock_get_referral

    “One referral by id, email address or external id (at least one is required): status, amount, referring member, notes, custom fields and dates.”

    Publisher declares: read-only yes · destructive no · open-world yes

    3 inputs
    • referral_idstring“The referral's id.”
    • emailstring“The referral's email address.”
    • external_idstring“The referral's external identifier.”
  • referralrock_list_rewards

    “List rewards, newest first by default: recipient, amount, status (Pending, Processing, Issued), payout type, eligibility and issue dates, the member and referral behind it.”

    Publisher declares: read-only yes · destructive no · open-world yes

    9 inputs
    • programstring“Program id, program name or program title.”
    • member_idstring“Only rewards of this member id.”
    • querystring“The recipient's email address, id, external id or member referral code.”
    • statusstring“Only rewards in this status.”
    • sortstring“Sort order (default Create_Dt_Desc).”
    • date_fromstring“Only rewards created after this date (yyyy-mm-dd).”
    • date_tostring“Only rewards created before this date (yyyy-mm-dd).”
    • offsetinteger“Starting index, 0 based (default 0).”
    • countinteger“Results per page, 1-200 (default 20).”
  • referralrock_list_pending_payouts

    “Payouts that are owed but not yet transferred: recipient, program, number of rewards and total amount.”

    Publisher declares: read-only yes · destructive no · open-world yes

    2 inputs
    • recipient_idstring“Only the payouts owed to this recipient id.”
    • include_ineligibleboolean“Also include payouts for rewards with an eligibility date in the future (default false).”
  • referralrock_list_payout_transactions

    “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.”

    Publisher declares: read-only yes · destructive no · open-world yes

    2 inputs
    • recipient_idstring“Only the transactions paid to this recipient id.”
    • transaction_idstring“Only this transaction id.”
  • referralrock_create_member

    “WRITE: creates a new member (advocate) in a referral program and returns the member with their referral code and share URL.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    9 inputs, 3 required
    • program_idstringrequired“Program id to add the member to (see referralrock_list_programs).”
    • first_namestringrequired“Member first name.”
    • emailstringrequired“Member email address.”
    • last_namestring“Member last name.”
    • phonestring“Member phone number.”
    • external_idstring“Your own id for this member, to link it to another system.”
    • referral_codestring“A custom referral code; Referral Rock generates one when left out.”
    • send_confirmation_emailboolean“Email the member the program's confirmation email (default false; needs confirm: true).”
    • confirmboolean“Must be true when send_confirmation_email is true: confirms an email goes to the member.”
  • referralrock_update_member

    “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).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    12 inputs
    • member_idstring“The member's id (preferred).”
    • referral_codestring“The member's referral code.”
    • emailstring“The member's current email address (needs program_id or program_name).”
    • external_idstring“The member's current external identifier (needs program_id or program_name).”
    • program_idstring“Program id; needed together with email or external_id (or give program_name).”
    • program_namestring“Program name; needed together with email or external_id (or give program_id).”
    • new_first_namestring“New first name.”
    • new_last_namestring“New last name.”
    • new_emailstring“New email address.”
    • new_phonestring“New phone number.”
    • new_external_idstring“New external identifier.”
    • disabledboolean“true disables the member, false re-enables.”
Show 3 more tools
  • referralrock_create_referral

    “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.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    12 inputs, 1 required
    • referral_codestringrequired“The referral code of the member who introduced the referral (see referralrock_list_members).”
    • first_namestring“Referral first name.”
    • last_namestring“Referral last name.”
    • emailstring“Referral email address.”
    • phonestring“Referral phone number.”
    • preferred_contactstring“Preferred way to contact the referral.”
    • external_idstring“Your own unique id for the referral (an order or customer id), to find it again.”
    • amountnumber“Order amount / total tied to the referral.”
    • company_namestring“Company name.”
    • notestring“Private note tied to the referral.”
    • statusstring“Initial status (default pending).”
    • confirmboolean“Must be true when status is qualified or approved: confirms rewards may be issued.”
  • referralrock_update_referral

    “WRITE: changes the status, amount or notes of an existing referral.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    10 inputs
    • referral_idstring“The referral's id (preferred).”
    • external_idstring“The referral's external identifier (needs program_id or program_name).”
    • emailstring“The referral's email address (needs program_id or program_name).”
    • program_idstring“Program id; needed together with external_id or email (or give program_name).”
    • program_namestring“Program name; needed together with external_id or email (or give program_id).”
    • statusstring“New status.”
    • amountnumber“New order amount / total (used for percentage rewards).”
    • notestring“New private note.”
    • public_notestring“New public note.”
    • confirmboolean“Must be true when status is qualified or approved, or amount is set: confirms rewards may be issued or changed.”
  • referralrock_record_customer

    “WRITE: reports a paying customer to Referral Rock.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    8 inputs, 2 required
    • emailstringrequired“The customer's email address; the match key against pending referrals and members.”
    • external_idstring“Your own id for this customer (for example a CRM id).”
    • first_namestring“Customer first name.”
    • last_namestring“Customer last name.”
    • phonestring“Customer phone number.”
    • amountnumber“Purchase amount; feeds percentage rewards (default 0).”
    • purchase_datestring“Purchase date, ISO 8601 (default: now, UTC).”
    • confirmbooleanrequired“Must be true: confirms a matching pending referral may be approved and its rewards issued.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 91
Tools with a description
100% of 15
Typical description length
288 characters

The tool set

Counted from the listing

Tools
15
Size of the list
about 5,244 tokens for an agent to load (characters ÷ 4)
Naming
15 of 15 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 15 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-24 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://referral-rock.usefulapi.io/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "referral-rock": {
      "url": "https://referral-rock.usefulapi.io/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "referral-rock": {
      "type": "http",
      "url": "https://referral-rock.usefulapi.io/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"referral-rock","type":"http","url":"https://referral-rock.usefulapi.io/mcp"}'
Claude Code
claude mcp add --transport http referral-rock https://referral-rock.usefulapi.io/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://referral-rock.usefulapi.io/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint referral-rock.usefulapi.io/mcpSession openedmatchesour test · 2026-10-24
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-24
Repository github.com/m190/usefulapi-mcpOpens publiclymatchesapi.github.com · 2026-10-24

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.usefulapi · 409 servers
GitHub owner
a personal account (m190)
Repository
github.com/m190/usefulapi-mcp
Stars
0
Repository age
91–180 days
Last push
0–30 days ago
Archived
no

Source: the registry entry and api.github.com · 2026-10-24.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-24. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.usefulapi/referral-rock

Answered from the data above

Is io.usefulapi/referral-rock safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.usefulapi/referral-rock need an API key or sign-in?

It opened a session without any credential on 2026-10-24. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.usefulapi/referral-rock been security tested?

Partly. 3 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Where is the source code of io.usefulapi/referral-rock?

In github.com/m190/usefulapi-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-24
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not run · an error was returned
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised13 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 13
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 2
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-24, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 448 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 15 tools, 0 resources, 1 prompt.
  4. 1,616 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-10-24; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
api.github.com · 2026-10-24
Hosting type
registry · 2026-10-24
MCP capability
prompts, tools
our test · 2026-10-24
Transport
streamable HTTP
registry · 2026-10-24
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-24
Lifecycle status
registry · 2026-10-24
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 91–180 days · stars: 0–9
api.github.com · 2026-10-24
Maintenance
api.github.com · 2026-10-24
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.usefulapi/referral-rock: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/io.usefulapi/referral-rock

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 4 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.usefulapi/referral-rock)](https://protocolprobe.com/mcp/servers/io.usefulapi/referral-rock)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology