← Home

@stripe/mcp

npm Repository Homepage

A command line tool for setting up Stripe MCP server

15
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 15 of 15)

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
0.2.1 3 / 13
0.2.0 3 / 13
0.1.4 3 / 13
0.1.3 3 / 13
0.1.2 3 / 13
0.1.1 2 / 13
0.1.0 2 / 13

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.0

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.