Ra-Pay MCP Server — Fiat Payments via Stripe

MCP server enabling AI agents to send fiat payments via Stripe Connect with a two-step confirmation flow. Designed for agent-initiated payments with human-in-the-loop confirmation — agents can initiate payment flows, pause for confirmation, then execute via Stripe.

Evaluated Mar 07, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Other payments stripe fiat ai-payments agent-payments mcp-server fintech
⚙ Agent Friendliness
65
/ 100
Can an agent use this?
🔒 Security
82
/ 100
Is it safe for agents?
⚡ Reliability
63
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
63
Documentation
62
Error Messages
62
Auth Simplicity
75
Rate Limits
68

🔒 Security

TLS Enforcement
96
Auth Strength
85
Scope Granularity
75
Dep. Hygiene
68
Secret Handling
82

Payment execution with real money. PCI scope. Stripe credentials critical. Two-step flow required for safety. HTTPS enforced.

⚡ Reliability

Uptime/SLA
65
Version Stability
62
Breaking Changes
60
Error Recovery
65
AF Security Reliability

Best When

A business wants AI agents to initiate payments as part of automated workflows — while keeping humans in the confirmation loop before money actually moves.

Avoid When

Autonomous agent payments without human review. FINANCIAL RISK: This server moves real money via Stripe — always test with Stripe test mode before production.

Use Cases

  • Agent-initiated payment workflows with human confirmation gates
  • Automating vendor or freelancer payments from business process agents
  • Building AI-powered expense and reimbursement workflows with Stripe backend
  • Testing and prototyping agent payment capabilities in development environments

Not For

  • Fully autonomous payments without human confirmation (requires two-step confirm)
  • Non-Stripe payment processors (Stripe Connect specific)
  • Consumer-facing payment collection (Stripe fee and terms apply)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: api_key
OAuth: No Scopes: No

Stripe Connect credentials required. Uses Stripe test/live mode. Two-step confirmation flow is built into the MCP server design — do not bypass.

Pricing

Model: free
Free tier: Yes
Requires CC: Yes

MCP server is free open source. Real payment costs are Stripe transaction fees. Use test mode for development.

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • FINANCIAL RISK: Sends real money — ALWAYS use Stripe test mode during development
  • Two-step confirmation is intentional — do not modify to bypass human review
  • PCI compliance: Stripe handles card data but Ra-Pay is in the payment flow chain
  • Stripe Connect requires platform account setup before use
  • Community implementation — verify against current Stripe Connect API

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Ra-Pay MCP Server — Fiat Payments via Stripe.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-07.

6232
Packages Evaluated
26150
Need Evaluation
173
Need Re-evaluation
Community Powered