Add BuyWhere MCP server (v1.0.4) to the official MCP Registry

[BuyWhere]

Add BuyWhere MCP server (v1.0.4) to the official MCP Registry

This PR adds the BuyWhere MCP server to the official MCP Registry using the proper io.github.BuyWhere/buywhere-mcp namespace (matching the canonical npm package @buywhere/mcp-server).

What is BuyWhere MCP?

Open-source MCP server for AI agent commerce. Search 50M+ products across 6 markets (SG, MY, TH, US, ID, AU) with hybrid FTS + vector search.

• Repo: https://github.com/BuyWhere/buywhere-mcp
• npm package: @buywhere/mcp-server v0.3.7
• Documentation: https://buywhere.ai/docs/guides/mcp
• Live API endpoint: https://api.buywhere.ai/mcp (canonical, working)

server.json details

• Namespace: io.github.BuyWhere/buywhere-mcp (matches npm package)
• Version: 1.0.4 (latest, includes the BUY-42672 Authorization: Bearer auth fix)
• Title: "BuyWhere MCP Server"
• Transports:
  • stdio via npx -y @buywhere/mcp-server (npm package)
  • streamable-http to https://api.buywhere.ai/mcp (remote endpoint)

Validation

$ /tmp/mcp-publisher validate /tmp/buywhere-mcp-server.json
Validating against https://registry.modelcontextprotocol.io...
✅ server.json is valid

Notes

• This PR uses the correct namespace (buywhere-mcp), not the legacy buywhere-api namespace from PR Add BuyWhere buywhere-api MCP server #1356
• The existing PR Add BuyWhere buywhere-api MCP server #1356 is using the old endpoint mcp.buywhere.io (deprecated, NXDOMAIN) and old namespace — closing that PR and merging this one is the recommended path
• v1.0.4 is in main of BuyWhere/buywhere-mcp (commit 4603226) with the Bearer auth fix
• Once merged, this entry will be available in MCP client discovery and the official registry browser

[BuyWhere]

Superseded — please close this PR (2026-06-12)

This PR is now redundant. The BuyWhere MCP server v1.0.4 is already live in the official MCP Registry via the canonical publish-mcp-registry workflow:

GET https://registry.modelcontextprotocol.io/v0/servers?search=buywhere

io.github.BuyWhere/buywhere-mcp v1.0.4
  - Description: "Open-source MCP server for AI agent commerce. Search 50M+ products across 6 markets."
  - Remotes: [https://api.buywhere.ai/mcp]
  - Packages: [@buywhere/mcp-server]

What happened:

1. This PR was opened with the correct buywhere-mcp namespace and v1.0.4
2. In parallel, I also created a v1.0.4 GitHub release in BuyWhere/buywhere-mcp
3. The publish-mcp-registry.yml workflow triggered on the release
4. The release workflow succeeded in publishing v1.0.4 to the official registry (it accepted the first submission that the release event triggered)
5. Now there are two v1.0.4 entries — this PR's and the one from the release

Recommendation: Close this PR. The release-triggered entry is already live. Keeping this PR open would either:

• (a) Reject as duplicate when the maintainer tries to merge, or
• (b) Result in a 409 conflict on the publish call

The new entry from the release workflow is functionally equivalent to this PR (same namespace, same version, same fields) — the maintainer's review work is the same either way.

CC: @vera (CEO, in case assignee needs direction)

[vera]

CC: @vera (CEO, in case assignee needs direction)

You've got the wrong user

[BuyWhere]

@maintainer friendly bump — this PR is part of BuyWherer's June 30 directory target. Any tweaks needed to land?