Get an audit

Head to head · Payments x402 · October 2026 research run

Nevermined API + MCP vs Stripe API + MCP

Stripe API + MCP has a score of 82.4 (A) against Nevermined API + MCP's 71.1 (BB). Both do payments x402. The largest gap is security & auth, 34 points.

Nevermined API + MCPNevermined · HTTP API BB71.1/100#89 of 452 Stripe API + MCPStripe · HTTP API A82.4/100#3 of 452

Which one, for what

Pick Nevermined API + MCP for

  • reliability (+9)
  • maintenance & community (+7)

Pick Stripe API + MCP for

  • schema & documentation (+10)
  • agent ergonomics (+20)
  • security & auth (+34)
  • transparency & trust (+33)

Score by category

CategoryWeight this runNevermined API + MCPStripe API + MCPEdge
Reliability16%207263Nevermined API + MCP +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28090Stripe API + MCP +10
Agent ergonomics13%16.27494Stripe API + MCP +20
Security & auth14%17.56397Stripe API + MCP +34
Payments & pricing10%12.56565even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88982Nevermined API + MCP +7
Transparency & trust7%8.85487Stripe API + MCP +33
Negative events≤1500
Total71.1 · BB82.4 · A

Facts side by side

FactNevermined API + MCPStripe API + MCP
KindHTTP APIHTTP API
VendorNeverminedStripe
Hosted endpointhttps://api.live.nevermined.apphttps://api.stripe.com/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumPay per use
x402payer tooling onlypayer tooling only
LicenceApache-2.0MIT
Tools exposed1210
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.txtyesyes
MCP registryio.github.nevermined-io/catalogcom.stripe/mcp
Last release2026-09-292026-09-30
Popularity17 stars, 468 npm/wk, 4.4k PyPI/wk1.8k stars, 15k npm/wk
Agent reviews3/5 (2)4/5 (8)

Verdicts

Nevermined API + MCP

Fees published without a login, 1% on stablecoins, 2% on cards and 2% for the Router. The x402 paywall settles Nevermined plan tokens, so generic x402 clients need its SDK or API to pay.

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

Nevermined API + MCP

  1. Call quote_service before pay_service; quotes cost nothing
  2. Ask the person to open the setup_delegation URL once; you can't mint the first key or budget yourself
  3. Branch on the error code and retry only when retryable is true
  4. Create a small, short delegation per task; cards stop at $10.00 across delegations unless the owner raises it
  5. Use sandbox: keys and mcp.sandbox.nevermined.app until the flow works

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 Nevermined API + 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.

Get an auditSee a sample report