MCP100 verdict
Use Stripe's remote MCP endpoint for supported payment workflows.
MCP100 Assessment
Editorial verdict
Use Stripe's remote MCP endpoint for supported payment workflows.
Reviewed 2026-07-24 · Next review 2026-10-24
Task Fit
Mapped
Specialized workflows
Trust
Reviewed
A dated editorial review is published on the MCP detail page.
Maintenance
Activity observed
A dated repository or package update is available; editorial maintenance review is still pending.
Popularity
Signals available
Visible usage signals are shown for discovery only, not as proof of safety.
Best for
- Searching Stripe documentation and support knowledge from an MCP client
- Inspecting Stripe account, balance, customer, product, and payment data
- Creating supported Stripe resources in a test account with human confirmation
Not ideal for
- Unattended production payment administration
- Workflows that require Stripe API operations not exposed by the current tool set
Avoid if
- The client cannot protect Stripe authorization tokens or secret keys
- You cannot require confirmation for write-capable payment tools
- Untrusted content can influence the same agent session without tool isolation
Trade-offs
- The hosted endpoint simplifies setup and uses OAuth, while the local package can use a secret key and therefore expands local credential-handling responsibility.
- Stripe labels the MCP service a public preview, so tools and behavior can change.
- Tool access is convenient but can create or modify payment-related resources within the granted Stripe account.
Evidence scope
Evidence
Popularity
1.7k MCP repository stars
No MCP-specific package metric is stored
Stars observed 2026-08-14T18:46:26.000Z · Downloads observation date unavailable
Shared repository stars are not MCP-specific.
No public package data is mapped to the reviewed MCP.
Maintenance
Publisher activity observed 2026-08-14T00:34:34Z
Current source snapshot
Trust review
Source relationship: First-party MCP
Reviewed 2026-07-24 · Next review 2026-10-24