Compared · stripe
8 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. 1 of 8 have a source repository that is no longer publicly reachable.
Scope: 8 servers, mostly mirrored from the MCP registry as of 2026-08-13. 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_connect | io.github.pipeworx-io | no flag | REVIEW | 84 | remote endpoint |
| io.github.CSOAI-ORG/meok-stripe-acp-checkout-mcp | io.github.CSOAI-ORG | no flag | REVIEW | 82 | pypi meok-stripe-acp-checkout-mcp |
| io.github.friendlygeorge/stripe-mcp-server | io.github.friendlygeorge | no flag | REVIEW | 82 | npm stripe-mcp-server |
| io.github.codespar/mcp-stripe | io.github.codespar | no flag | REVIEW | 78 | npm @codespar/mcp-stripe |
| io.github.codespar/mcp-stripe-acp | io.github.codespar | no flag | REVIEW | 78 | npm @codespar/mcp-stripe-acp |
| io.github.CSOAI-ORG/stripe-billing-mcp | io.github.CSOAI-ORG | no flag | REVIEW | 75 | pypi stripe-billing-mcp |
| io.github.lordbasilaiassistant-sudo/stripe-analytics | io.github.lordbasilaiassistant-sudo | no flag | REVIEW | 75 | npm mcp-stripe-analytics |
| io.github.infoinlet-marketplace/mcp-stripe | io.github.infoinlet-marketplace | repo unreachable | REVIEW | 77 | npm @infoinlet/mcp-stripe |
“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.