← Home

@stripe/mcp

npm Repository Homepage

A command line tool for setting up Stripe MCP server

8
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

nazli-stripestripejsjordand-stripearashn-stripemaxliu-stripejackieosborn-stripebillfinn-stripelins-stripestripe-bindingsjil-stripetomas-stripebibek-striperado-stripeyuluomengfkuo-stripechaves-stripeporter-stripelemuel-stripengrubb-stripecchalstrom-stripecharliecruzan-stripemattpatt-stripeericfrank-stripetomer-stripemindy-stripetennhard-stripejackokerman-stripeianjabour-stripestegs-stripejeremyg-stripeebarrenechea-stripestevekaliski-stripematebek-stripehenryx-stripekovalev-stripetylerkrupickastripeaywang-striperaulfdm-stripetimbennett-stripedavidme-stripesvenugopal-stripealexander-stripetoluo-stripetillh-stripewooj-stripejoyceqin-stripejaynewstrom-stripegbirch-stripecttsailuisv-stripelamflam-stripetjclawson-stripematv-stripelng-stripemats-stripesamer-stripe

Keywords

mcpmodelcontextprotocolstripe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): New maintainers (tjclawson-stripe, matv-stripe) are Stripe org accounts; internal team rotation, not a takeover. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped @stripe package; Levenshtein match to 'yup' is a false positive with no actual similarity in purpose or name. ai

Versions (showing 8 of 8)

Version Deps Published
0.3.3 2 / 16
0.3.2 2 / 16
0.3.1 2 / 16
0.3.0 2 / 16
0.2.5 3 / 16
0.2.4 3 / 16
0.2.3 3 / 14
0.2.2 3 / 14

v0.3.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.5

2 findings
HIGH Publisher changed: stevekaliski-stripe → matv-stripe (on 2025-10-29) provenance

This version was published by a different npm account than previous versions on 2025-10-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.4

2 findings
HIGH Publisher changed: stevekaliski-stripe → matv-stripe (on 2025-08-13) provenance

This version was published by a different npm account than previous versions on 2025-08-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.