@buywhere/mcp-server MIT 21 versions

@buywhere/mcp-server

npm Repository Homepage

BuyWhere MCP Server — Agent-native product catalog API for AI agents via Model Context Protocol

21

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

richieboyz18

Keywords

buywheremcpmcp-servermodel-context-protocolproduct-searchproduct-search-apiproduct-search-mcpagent-product-searchmcp-commerce-searchecommerce-apiecommerceshopping-apishopping-agentshoppingprice-comparisoncompare-pricesprice-trackerdeal-finderdeal-discoverycatalog-searchproduct-catalogcross-bordercross-border-shoppingcross-border-commercemulti-currencyreal-time-pricingsoutheast-asiasingaporesea-marketsus-marketsai-agentai-commerceagent-commerceagent-shoppingagent-to-agenta2agoogle-a2allmai-toolsclaude-desktopcursorclinewindsurfopen-codecodexcontinue-devsmitherymcp-toolstypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Single version anomaly; no other risk signals present. Likely a one-off local publish rather than a supply chain concern.	ai	2026/05/30
install-scripts	install-script:postinstall	AI (install-scripts): Postinstall only prints a welcome message; no network access or arbitrary code execution.	ai	2026/05/18

Versions (showing 21 of 21)

Version	Deps	Published
0.3.11	1 / 2	2026-05-08
0.3.10	1 / 2	2026-05-07
0.3.9	1 / 2	2026-05-07
0.3.8	1 / 2	2026-05-06
0.3.7	1 / 2	2026-05-06
0.3.6	1 / 2	2026-05-05
0.3.5	1 / 2	2026-05-04
0.3.4	1 / 2	2026-05-03
0.3.3	1 / 2	2026-05-03
0.3.2	1 / 2	2026-05-03
0.3.1	1 / 2	2026-05-03
0.3.0	1 / 2	2026-05-03
0.2.1	1 / 2	2026-05-03
0.2.0	1 / 3	2026-05-03
0.1.6	1 / 3	2026-05-02
0.1.5	1 / 2	2026-05-02
0.1.4	1 / 2	2026-05-02
0.1.3	1 / 3	2026-05-01
0.1.2	1 / 3	2026-05-01
0.1.1	1 / 3	2026-04-29
0.1.0	1 / 3	2026-04-29

v0.3.11

1 finding

LOW No provenance attestation provenance

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

v0.3.10

1 finding

LOW No provenance attestation provenance

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

v0.3.9

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: richieboyz18.

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: richieboyz18.

LOW No provenance attestation provenance

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

v0.3.4

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: richieboyz18.

LOW No provenance attestation provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node -e "try{require('fs').existsSync(require('path').join(__dirname,'dist','index.js'))&&console.log('\n ✦ BuyWhere MCP server v0.3.0 installed\n › Set BUYWHERE_API_KEY and add to your MCP client config\n › Docs: https://github.com/BuyWhere/buywhere/tree/main/packages/mcp-server\n')}catch(e){}"

LOW No provenance attestation provenance

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

v0.3.0

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node -e "try{require('fs').existsSync(require('path').join(__dirname,'dist','index.js'))&&console.log('\n ✦ BuyWhere MCP server v0.3.0 installed\n › Set BUYWHERE_API_KEY and add to your MCP client config\n › Docs: https://github.com/BuyWhere/buywhere/tree/main/packages/mcp-server\n')}catch(e){}"

LOW No provenance attestation provenance

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

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.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.