Compared · stripe
13 Stripe MCP servers. Which one to use.
Every Stripe server we index, with whether its source is still reachable and whether we hold a screening verdict. 2 of 13 have a source repository that is no longer publicly reachable.
Scope: 13 servers, mostly mirrored from the MCP registry as of 2026-10-23. Most servers whose authors never published to the registry are absent, so treat this as close to the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| Stripe MCP by InsightfulPipe | com.insightfulpipe | no flag | REVIEW | 95 | remote endpoint |
| NordicMCP — Stripe | eu.nordicmcp | no flag | REVIEW | 92 | remote endpoint |
| Stripe_connect | io.github.pipeworx-io | no flag | REVIEW | 90 | remote endpoint |
| Stripe MCP | io.github.robinafaruqia | no flag | REVIEW | 89 | npm @devtechtricks/stripe-mcp |
| io.github.mrfentmen/stripe-mcp | io.github.mrfentmen | no flag | REVIEW | 85 | npm @mrfentmen/stripe-mcp |
| io.github.theluckystrike/stripe-billing | io.github.theluckystrike | no flag | REVIEW | 85 | not published |
| Stripe | io.github.mcp-dir | no flag | REVIEW | 83 | remote endpoint |
| io.github.CSOAI-ORG/stripe-billing-mcp | io.github.CSOAI-ORG | no flag | REVIEW | 77 | pypi stripe-billing-mcp |
| io.github.friendlygeorge/stripe-mcp-server | io.github.friendlygeorge | no flag | REVIEW | 77 | npm stripe-mcp-server |
| io.github.codespar/mcp-stripe | io.github.codespar | no flag | REVIEW | 73 | npm @codespar/mcp-stripe |
| io.github.codespar/mcp-stripe-acp | io.github.codespar | no flag | REVIEW | 73 | npm @codespar/mcp-stripe-acp |
| io.github.infoinlet-marketplace/mcp-stripe | io.github.infoinlet-marketplace | repo unreachable | REVIEW | 71 | npm @infoinlet/mcp-stripe |
| io.github.lordbasilaiassistant-sudo/stripe-analytics | io.github.lordbasilaiassistant-sudo | repo unreachable | REVIEW | 70 | npm mcp-stripe-analytics |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.