# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/payman-vs-stripe-mcp
- Markdown: https://www.anchorterminal.com/compare/payman-vs-stripe-mcp.md (~1,400 tokens)
- Slim: https://www.anchorterminal.com/compare/payman-vs-stripe-mcp.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/payman-vs-stripe-mcp.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-04

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.

- Payman Genie MCP: grade D, 53/100, rank #337 of 452. Markdown https://www.anchorterminal.com/tools/payman.md · JSON https://www.anchorterminal.com/api/v1/tools/payman.json
- Stripe API + MCP: grade A, 82.4/100, rank #3 of 452. Markdown https://www.anchorterminal.com/tools/stripe-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/stripe-mcp.json

## Which one, for what

Pick Payman Genie MCP for nothing in particular (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 | Payman Genie MCP | Stripe API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 25 | 63 | Stripe API + MCP +38 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 56 | 90 | Stripe API + MCP +34 |
| Agent ergonomics | 13% (16.2 this run) | 68 | 94 | Stripe API + MCP +26 |
| Security & auth | 14% (17.5 this run) | 80 | 97 | Stripe API + MCP +17 |
| Payments & pricing | 10% (12.5 this run) | 35 | 65 | Stripe API + MCP +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 60 | 82 | Stripe API + MCP +22 |
| Transparency & trust | 7% (8.8 this run) | 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

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

- [Skyfire API + MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/skyfire-vs-stripe-mcp.md)
- [Stripe API + MCP vs Tempo](https://www.anchorterminal.com/compare/stripe-mcp-vs-tempo.md)
- [Crossmint API + Docs MCP vs Payman Genie MCP](https://www.anchorterminal.com/compare/crossmint-vs-payman.md)
- [Crossmint API + Docs MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/crossmint-vs-stripe-mcp.md)
- [Payman Genie MCP vs Skyfire API + MCP](https://www.anchorterminal.com/compare/payman-vs-skyfire.md)
- [Nevermined API + MCP vs Payman Genie MCP](https://www.anchorterminal.com/compare/nevermined-vs-payman.md)
- [Nevermined API + MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/nevermined-vs-stripe-mcp.md)