Ra Pay
NPM · @RAPAY/MCP-SERVER
Send fiat payments via MCP with two-step confirmation and Stripe Connect.
Available components
Last scanned (2 hours ago)
Scores higher than 58% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency13
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 750 tokens (~107/item across 7 items; 7 tools + 0 resources), lean.Pass
- 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 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 −1
- Stability: pass → 0.93 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 15 Oct 26 −2
- Stability: pass → 0.83 functional
- 14 Oct 26 0
- Stability: 0.97 → pass security
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 · Analysed npm/@rapay/mcp-server@1.2.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
ra_balance ~28
Check available balance in your Ra Pay account. Returns current balance, pending amounts, and payout schedule.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ra_dashboard ~33
Open the Stripe Dashboard in the user's browser. Provides access to the full Stripe account overview including payments, payouts, and settings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ra_dispute ~47
Open the Stripe Disputes page in the user's browser. Disputes and chargebacks must be managed through the Stripe Dashboard interface. Respond to disputes within the timeframe to avoid auto-loss.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ra_history ~52
Get transaction history from your Ra Pay account. Returns recent payments, subscriptions, and refunds with timestamps and status.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of transactions to retrieve (default: 10, max: 100) |
No output schema declared.
No examples provided.
ra_refund ~41
SENSITIVE: Open Stripe Dashboard to process refunds. For security, refunds are processed through the Stripe Dashboard interface. This opens your browser to the refund management page.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ra_send ~518
SENSITIVE: Send a payment. TWO-STEP PROCESS REQUIRED: Step 1: Call with user_confirmed=false to get fee preview (NO payment is made). Step 2: Show the fee_breakdown from the response to the user and ask them to confirm. Step 3: ONLY after user explicitly approves the fee, call again with user_confirmed=true. A 2% Ra Pay application fee applies. The preview shows the Ra Pay application fee before any money moves. COMPLIANCE SCREENING REQUIRED: Before processing, you MUST verify the business_purpose does NOT contain: (1) P2P patterns: friend, family, roommate, reimbursement for personal expenses, splitting bills, payback, loan, gift, birthday, holiday (2) Money laundering red flags: gift cards, prepaid cards, cryptocurrency purchase, wire transfer (3) Vague purposes: 'for services', 'payment', 'transfer' without specifics (4) Gibberish: repetitive characters (aaaa), random letters (adlkfjal), or repeated words (test test test). If detected, WARN the user that Ra Pay is for business transactions only and ask them to provide a legitimate business purpose.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount to send in USD cents (e.g., 10000 = $100.00). Minimum: 100 cents ($1.00) |
| business_purpose | string | yes | Business purpose for this payment (10-200 characters). Required for compliance. Must describe actual goods or services rendered (e.g., 'Logo design work', 'API consulting'). REJECT purposes containin… |
| recipient_id | string | yes | Stripe connected account ID (format: acct_xxx). Must be a valid Stripe account. |
| user_confirmed | boolean | yes | REQUIRED. Must be false on first call to get fee preview. Only set to true AFTER showing user the fee_breakdown and getting their explicit approval. |
No output schema declared.
No examples provided.
ra_whoami ~31
Check account status and identity. Returns user ID, Stripe account status, verification status, and account tier.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Ra Pay MCP server?
Ra Pay runs locally as an npm package, launched with npx -y @rapay/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rapay/mcp-server
claude mcp add ai-rapay-mcp-server -- npx -y @rapay/mcp-server
What is the Ra Pay MCP server?
Ra Pay is an MCP server listed in the public MCP registry as ai.rapay/mcp-server. Send fiat payments via MCP with two-step confirmation and Stripe Connect. This page covers its npm package (@rapay/mcp-server).
Is the Ra Pay MCP server safe to use?
Ra Pay scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Ra Pay MCP server expose?
Ra Pay exposes 7 tools: ra_send, ra_refund, ra_balance, ra_history, ra_whoami, and 2 more. Their descriptions and schemas cost roughly 750 tokens of context every time the server is loaded.
Is the Ra Pay MCP server still maintained?
Ra Pay 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.
What licence is the Ra Pay MCP server under?
Ra Pay declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.