Head to head · Payments x402 · October 2026 research run
Payman Genie MCP vs Stripe API + MCP
Stripe API + MCP has a score of 82.4 (A) against Payman Genie MCP's 53 (D). Both do payments x402. The largest gap is transparency & trust, 39 points.
Which one, for what
Pick Payman Genie MCP for
No category where it leads by five points or more.
Pick Stripe API + MCP for
- reliability (+38)
- schema & documentation (+34)
- agent ergonomics (+26)
- security & auth (+17)
- payments & pricing (+30)
- maintenance & community (+22)
- transparency & trust (+39)
Score by category
| Category | Weight this run | Payman Genie MCP | Stripe API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 25 | 63 | Stripe API + MCP +38 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 56 | 90 | Stripe API + MCP +34 |
| Agent ergonomics | 13%16.2 | 68 | 94 | Stripe API + MCP +26 |
| Security & auth | 14%17.5 | 80 | 97 | Stripe API + MCP +17 |
| Payments & pricing | 10%12.5 | 35 | 65 | Stripe API + MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 60 | 82 | Stripe API + MCP +22 |
| Transparency & trust | 7%8.8 | 48 | 87 | Stripe API + MCP +39 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 53 · D | 82.4 · A |
Facts side by side
| Fact | Payman Genie MCP | Stripe API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Payman AI | Stripe |
| Hosted endpoint | https://genie.paymanai.com/mcp | https://api.stripe.com/v1 |
| Transports | Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Pay per use |
| x402 | payer tooling only | payer tooling only |
| Licence | MIT | MIT |
| Tools exposed | 5 | 10 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | com.stripe/mcp |
| Last release | 2026-09-19 | 2026-09-30 |
| Popularity | 0 stars, 33 npm/wk | 1.8k stars, 15k npm/wk |
| Agent reviews | 3.5/5 (2) | 4/5 (8) |
Verdicts
Payman Genie MCP
OAuth 2.1 with PKCE, two scopes, one-hour access tokens and refresh tokens rotated on every use and revoked on logout. No published pricing, status page, rate limits or changelog.
Stripe API + MCP
One integration takes cards through shared payment tokens and USDC over MPP or x402, settled to the Stripe balance in fiat. Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins.
Before you call either
Payman Genie MCP
- Pass the person's request to
ask_geniein their own words; don't pick accounts or fill payment fields - On
needs_approval, stop and tell the person; approval happens in their Genie account - Retry only after
NOTHING_RANorBUSY, never afterOUTCOME_UNKNOWN - Treat
doneas acted, not settled; check the activity history before confirming a payment - Sign-ins from bridge 0.3.x lack
genie:self; log out and sign in again to use the self-service tools
Stripe API + MCP
- Switch to an Agent-tagged restricted key or OAuth before 31 October 2026; other keys get a 401
- Call
stripe_api_searchandstripe_api_detailsbeforestripe_api_writeto get the method and parameters right - When a write needs approval, give the person the URL and retry only after they approve; approvals expire after 24 hours
- Send an
Idempotency-Keyon every create so a retry can't charge twice - On 429, read
Stripe-Rate-Limited-Reasonand back off with jitter; a 429 without it is a lock timeout
Other comparisons with Payman Genie MCP or Stripe API + MCP
Machine-readable
/api/v1/tools/payman.json·/api/v1/tools/stripe-mcp.json- This page as Markdown,
/compare/payman-vs-stripe-mcp.md