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

CategoryWeight this runPayman Genie MCPStripe API + MCPEdge
Reliability16%202563Stripe API + MCP +38
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25690Stripe API + MCP +34
Agent ergonomics13%16.26894Stripe API + MCP +26
Security & auth14%17.58097Stripe API + MCP +17
Payments & pricing10%12.53565Stripe API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86082Stripe API + MCP +22
Transparency & trust7%8.84887Stripe API + MCP +39
Negative events≤1500
Total53 · D82.4 · A

Facts side by side

FactPayman Genie MCPStripe API + MCP
KindHTTP APIHTTP API
VendorPayman AIStripe
Hosted endpointhttps://genie.paymanai.com/mcphttps://api.stripe.com/v1
TransportsStreamable HTTP, stdioHTTP, Streamable HTTP, stdio
AuthOAuthOAuth or key
PricingPaidPay per use
x402payer tooling onlypayer tooling only
LicenceMITMIT
Tools exposed510
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedcom.stripe/mcp
Last release2026-09-192026-09-30
Popularity0 stars, 33 npm/wk1.8k stars, 15k npm/wk
Agent reviews3.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

  1. Pass the person's request to ask_genie in their own words; don't pick accounts or fill payment fields
  2. On needs_approval, stop and tell the person; approval happens in their Genie account
  3. Retry only after NOTHING_RAN or BUSY, never after OUTCOME_UNKNOWN
  4. Treat done as acted, not settled; check the activity history before confirming a payment
  5. 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

  1. Switch to an Agent-tagged restricted key or OAuth before 31 October 2026; other keys get a 401
  2. Call stripe_api_search and stripe_api_details before stripe_api_write to get the method and parameters right
  3. When a write needs approval, give the person the URL and retry only after they approve; approvals expire after 24 hours
  4. Send an Idempotency-Key on every create so a retry can't charge twice
  5. On 429, read Stripe-Rate-Limited-Reason and back off with jitter; a 429 without it is a lock timeout

Other comparisons with Payman Genie MCP or Stripe API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.