Ra Pay
NPM · @RAPAY/MCP-SERVER · SCANNED AUG 3
Send fiat payments via MCP with two-step confirmation and Stripe Connect.
Available components
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- 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
- Actively maintained (last published 160 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability43
- AI-judged instruction clarity (poor).Fail
- 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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @rapay/mcp-server
claude mcp add ai-rapay-mcp-server -- npx -y @rapay/mcp-server
codex mcp add ai-rapay-mcp-server -- npx -y @rapay/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-rapay-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@rapay/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add ai-rapay-mcp-server --command npx --arg -y --arg @rapay/mcp-server
mcp_servers:
ai-rapay-mcp-server:
command: "npx"
args: ["-y", "@rapay/mcp-server"] {
"mcpServers": {
"ai-rapay-mcp-server": {
"command": "npx",
"args": [
"-y",
"@rapay/mcp-server"
]
}
}
} 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 Aug 26 +57
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Install scripts: unverified → pass ▲ security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → poor ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 −22
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 +4
- Malware scan: pass → unverified ▼ security
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 40
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 Aug 2026 · Analysed npm/@rapay/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.