SkillTotal

Is BuyWhere MCP safe?

No malicious indicators - review capabilities before installing
Notable — review in context (capabilities are not malware):
  • Node.js network egress
  • MCP tool surface detected

What to do: Nothing here argues against installing it. Grant the capabilities it lists only if you expect the tool to need them.

BuyWhere MCP is an npm package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators. It can: mcp tools detected and network egress — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).

buywhere-mcp 1.0.2

npm_package · npm:buywhere-mcp
LOW
0
/ 100 risk score
Snapshot · scanned Oct 8, 2026 · buywhere-mcp@1.0.2 · engine 0.56.4 / ruleset 62

Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of BuyWhere MCP's authors. Report a false positive.

Capabilities — what this component can do (not a risk score):
mcp tools detectednetwork egress

Behavioral traits

How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.

Tool surface
Tool Usage
Network egress
Interaction & Communication / Direct Communication

Findings (2)

MEDIUMNode.js network egressST-NET-NODE

The component makes outbound network requests.

dist/index.js:49-49 
const res = await fetch(url.toString(), {
dist/index.js:63-63 
const res = await fetch(`${BASE_URL}${path}`, {

Why it matters: Usually legitimate, but confirm the destinations are expected and no sensitive data leaves.

Fix: Confirm the destination hosts are expected and that no sensitive data is sent off-host.

LOWMCP tool surface detectedST-MCP-DETECTED

An MCP tool surface (manifest or tool definitions) was found.

dist/index.js:131-131 
const server = new Server({ name: "buywhere-mcp", version: "0.1.0" }, {
dist/index.js:140-140 
server.setRequestHandler(ListToolsRequestSchema, async () => ({
dist/index.js:253-253 
server.setRequestHandler(CallToolRequestSchema, async (request) => {
dist/index.js:484-484 
const transport = new StdioServerTransport();

Why it matters: Just context — review which tools it offers and their permissions.

Fix: Review the declared MCP tools and their permissions.

Check your own component

Run the same evidence-backed scan on any MCP server, agent skill, or package.

Scan your own component

How we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →