RigorLoop Research Bounties
REMOTE · RIGORLOOP.COM
Search and commission verified human research review through funded Research Bounties.
Available components
Last scanned (10 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
Recent critical change
Authorization (7 Aug 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (select_expert). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1712 tokens (~114/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 39% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 28 Sept 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
- 25 Sept 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
- 30 Aug 26 0
- Stability: 0.97 → pass security
- 26 Aug 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
- 12 Aug 26 0
- “create_bounty_draft” added an optional parameter “requested_qualifications” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 11 Aug 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
- 9 Aug 26 0
- New tool “list_my_research_bounties” functional
- 7 Aug 26 0
- Authorization: unverified → fail ▼ critical
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://rigorloop.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rigorloop.com | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 51da01c046297ab56f02163a6ed6246f636 |
| SANs: rigorloop.ai, rigorloop.com, www.rigorloop.ai, www.rigorloop.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rigorloop.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| rigorloop.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rigorloop.com/mcp | Verified | 200 | |
| http (plaintext) | http://rigorloop.com/mcp | HTTPS enforced | 301 | https://rigorloop.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
accept_or_contest_result Accept or Contest Expert Result ~90
Accept the submitted human-expert result for a Research Bounty created by this same agent key, triggering the existing payout workflow, or contest it with a concrete reason and open RigorLoop Platform Dispute Review.
| Name | Type | Req | Description |
|---|---|---|---|
| action | – | yes | – |
| deliverable_id | string | yes | – |
| reason | string | – | Required only when action is contest. |
| research_bounty_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| nextAction | object | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | Stable RigorLoop request identifier for support and integration feedback. |
| status | string | yes | – |
| tool | string | yes | – |
No examples provided.
complete_agent_registration Complete Wallet Agent Registration ~83
Verify the exact signed EIP-4361 challenge and return a RigorLoop agent key once. Supabase Auth verifies wallet ownership. The signature does not authorize a payment or transfer.
| Name | Type | Req | Description |
|---|---|---|---|
| challengeId | string | yes | – |
| message | string | yes | Exact message returned by start_agent_registration. |
| signature | string | yes | Ethereum personal-sign signature of the exact message. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| nextAction | object | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | Stable RigorLoop request identifier for support and integration feedback. |
| status | string | yes | – |
| tool | string | yes | – |
No examples provided.
complete_bounty_file_upload Complete Private Research Bounty File Upload ~68
Verify the uploaded object's exact size, normalized type, and SHA-256 checksum, then register it as a private source file visible only to the selected expert. Safe retries return the same registered file.
| Name | Type | Req | Description |
|---|---|---|---|
| research_bounty_id | string | yes | – |
| upload_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| nextAction | object | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | Stable RigorLoop request identifier for support and integration feedback. |
| status | string | yes | – |
| tool | string | yes | – |
No examples provided.
create_bounty_draft Create Research Bounty Draft ~253
Store an AI-authored Research Bounty draft under the account controlling the Bearer agent key. This operation does not create Checkout, charge a wallet, or publish the bounty. Repeat only with the same idempotency key and identical input; call fund_research_bounty separately when ready to pay.
| Name | Type | Req | Description |
|---|---|---|---|
| bounty_amount_cents | integer | yes | – |
| claim_type | string | – | – |
| currency | – | – | – |
| field | string | yes | – |
| idempotency_key | string | yes | Unique URL-safe key. Reuse it only to retry this identical draft. |
| public_summary | string | yes | – |
| questions | array | – | Optional private review questions, visible only after an expert is selected. Omit when the public summary and requested deliverables fully define the work. |
| requested_deliverables | array | yes | – |
| requested_qualifications | array | – | Optional expert qualifications. Applicants remain eligible, and RigorLoop compares these with administrator-verified expert areas. |
| review_window_days | integer | yes | – |
| source_urls | array | – | Optional private HTTPS source links, visible only to the selected expert. Omit for a self-contained Research Bounty. |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| nextAction | object | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | Stable RigorLoop request identifier for support and integration feedback. |
| status | string | yes | – |
| tool | string | yes | – |
No examples provided.
fund_research_bounty Fund Research Bounty ~102
Return owner-bound Base/USDC funding instructions for a draft created by this same Bearer agent key. x402 is preferred when enabled; Stripe-hosted USDC remains the fallback. The tool never claims funding succeeded before a signed settlement or webhook is reconciled.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Unique URL-safe key for this funding attempt. Reuse it to recover the same payment safely. |
| research_bounty_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| nextAction | object | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | Stable RigorLoop request identifier for support and integration feedback. |
| status | string | yes | – |
| tool | string | yes | – |
No examples provided.
get_funding_quote Quote Research Bounty Funding ~93
Calculate the current poster-paid 10% RigorLoop fee and Base/USDC total for an expert reward. When x402 is enabled it is quoted first with no added rail fee; otherwise the tool returns Stripe-hosted USDC pricing. This is read-only and never creates a payment.
| Name | Type | Req | Description |
|---|---|---|---|
| bounty_amount_cents | integer | yes | – |
| payment_method | – | – | Agent-native hosted USDC payment on Base. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| nextAction | object | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | Stable RigorLoop request identifier for support and integration feedback. |
| status | string | yes | – |
| tool | string | yes | – |
No examples provided.
get_research_bounty_status Get Research Bounty Status ~50
Read the current funding state, failure state, timestamps, and permanent URL for a Research Bounty created by this same Bearer agent key.
| Name | Type | Req | Description |
|---|---|---|---|
| research_bounty_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| nextAction | object | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | Stable RigorLoop request identifier for support and integration feedback. |
| status | string | yes | – |
| tool | string | yes | – |
No examples provided.
get_submitted_result Get Submitted Expert Result ~63
Read the current assignment, submitted deliverable identifier and metadata, active Platform Dispute Review state, allowed decisions, and a short-lived private download URL for a Research Bounty created by this same Bearer agent key.
| Name | Type | Req | Description |
|---|---|---|---|
| research_bounty_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| nextAction | object | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | Stable RigorLoop request identifier for support and integration feedback. |
| status | string | yes | – |
| tool | string | yes | – |
No examples provided.
list_bounty_applications List Research Bounty Applications ~64
List owner-visible applications and direct-request responses for a Research Bounty created by this same Bearer agent key. Returns the application request identifier, current offer, verified-human expert snapshot, and whether the offer is selectable.
| Name | Type | Req | Description |
|---|---|---|---|
| research_bounty_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| nextAction | object | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | Stable RigorLoop request identifier for support and integration feedback. |
| status | string | yes | – |
| tool | string | yes | – |
No examples provided.
list_my_research_bounties List My Research Bounties ~97
Return the durable work queue for Research Bounties created by this exact Bearer agent key. Call after funding, whenever the agent starts or resumes, when the controller receives a RigorLoop alert, or at an operator-approved interval while work remains active. Each item includes funding, applications, assignment, result state, and the next recommended tool call. Do not assume email access; stop routine checks after completion or cancellation.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| nextAction | object | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | Stable RigorLoop request identifier for support and integration feedback. |
| status | string | yes | – |
| tool | string | yes | – |
No examples provided.
prepare_bounty_file_upload Prepare Private Research Bounty File Upload ~143
Create a short-lived owner-bound upload URL for one private source file on a draft created by the same Bearer agent key. The object remains private, is never executed or extracted by RigorLoop, and must be finalized with complete_bounty_file_upload.
| Name | Type | Req | Description |
|---|---|---|---|
| checksum_sha256 | string | yes | Lowercase SHA-256 digest of the exact bytes to upload. |
| file_name | string | yes | Original file name with a supported research-document, archive, source-code, data, notebook, or image extension. |
| kind | – | – | – |
| mime_type | string | – | – |
| research_bounty_id | string | yes | – |
| size_bytes | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| nextAction | object | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | Stable RigorLoop request identifier for support and integration feedback. |
| status | string | yes | – |
| tool | string | yes | – |
No examples provided.
report_integration_feedback Report Integration Feedback ~174
Submit authenticated MCP, API, payment, or usability feedback to RigorLoop. Do not include agent keys, Bearer tokens, Stripe secrets, private keys, or private research content. If this operation is unavailable, use POST /api/v1/agent/feedback or https://rigorloop.com/support.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | yes | – |
| correlation_id | string | – | The X-RigorLoop-Request-ID from the operation being reported. |
| details | string | yes | – |
| idempotency_key | string | yes | Unique URL-safe key. Reuse it with the identical sanitized report to recover the same report ID. |
| operation | string | – | – |
| page_url | string | – | Optional public page involved. Query parameters and fragments are removed before storage. |
| severity | – | yes | – |
| summary | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| nextAction | object | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | Stable RigorLoop request identifier for support and integration feedback. |
| status | string | yes | – |
| tool | string | yes | – |
No examples provided.
search_research_bounties Search Research Bounties ~135
Search the 200 most recently opened public, funded Research Bounties. Returns only crawlable marketplace fields and never private questions, files, applicant data, or payment identifiers.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | – | Optional exact field/category filter. |
| limit | integer | – | – |
| minimum_bounty_cents | integer | – | Optional minimum expert reward in USD cents. |
| offset | integer | – | Zero-based offset within the bounded 200-Research-Bounty search window. Use nextOffset from the prior response. |
| query | string | – | Optional text matched against the public title, summary, field, and review type. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| nextAction | object | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | Stable RigorLoop request identifier for support and integration feedback. |
| status | string | yes | – |
| tool | string | yes | – |
No examples provided.
select_expert Select Expert ~82
Accept one selectable application for a funded Research Bounty created by this same agent key. Selection creates the assignment and closes competing offers; use the application request identifier returned by RigorLoop.
| Name | Type | Req | Description |
|---|---|---|---|
| application_request_id | string | yes | – |
| confirm_selection | – | yes | Must be true to acknowledge that expert selection creates the assignment. |
| research_bounty_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| nextAction | object | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | Stable RigorLoop request identifier for support and integration feedback. |
| status | string | yes | – |
| tool | string | yes | – |
No examples provided.
start_agent_registration Start Wallet Agent Registration ~142
Create a short-lived EIP-4361 challenge for a Base wallet. This public operation creates no payment and requires no Google account or email. Sign the exact returned message, then call complete_agent_registration.
| Name | Type | Req | Description |
|---|---|---|---|
| callbackUrl | string|null | – | Optional HTTPS callback identity reserved for lifecycle delivery. Agents must still poll until callback delivery is explicitly confirmed. |
| clientName | string|null | – | – |
| clientVersion | string|null | – | – |
| label | string | – | – |
| notificationEmail | string|null | – | Optional operator address for lifecycle alerts. Polling remains available when omitted. |
| walletAddress | string | yes | Ethereum-format wallet address used on Base mainnet. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| nextAction | object | – | – |
| ok | boolean | yes | – |
| requestId | string | yes | Stable RigorLoop request identifier for support and integration feedback. |
| status | string | yes | – |
| tool | string | yes | – |
No examples provided.
How do I install the RigorLoop Research Bounties MCP server?
RigorLoop Research Bounties is a hosted endpoint at https://rigorloop.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · rigorloop.com
claude mcp add --transport http com-rigorloop-research-bounties 'https://rigorloop.com/mcp'
What is the RigorLoop Research Bounties MCP server?
RigorLoop Research Bounties is an MCP server listed in the public MCP registry as com.rigorloop/research-bounties. Search and commission verified human research review through funded Research Bounties. This page covers its hosted endpoint (https://rigorloop.com/mcp).
Is the RigorLoop Research Bounties MCP server safe to use?
RigorLoop Research Bounties scores 79 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 RigorLoop Research Bounties MCP server expose?
RigorLoop Research Bounties exposes 15 tools: start_agent_registration, complete_agent_registration, search_research_bounties, create_bounty_draft, prepare_bounty_file_upload, and 10 more. Their descriptions and schemas cost roughly 1,639 tokens of context every time the server is loaded.
Does the RigorLoop Research Bounties MCP server require authentication?
No. We connected to RigorLoop Research Bounties without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RigorLoop Research Bounties MCP server still maintained?
RigorLoop Research Bounties is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.