Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.sukrutkrdg/x402-bazaar-mcp

NPM · X402-BAZAAR-MCP

Check, then act, on Base and NEAR: token-safety gates, then swaps at the best price — over x402.

Available components

0 this week 79 Trust /100

Last scanned (4 hours ago)

Scores higher than 61% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 32 of 118 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 202 tokens (~101/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 22 Oct 26 0
    • Stability: 0.97 → pass security
  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 17 Oct 26 +3
    • Stability: 0.80 → pass security
  • 15 Oct 26 −3
    • Stability: pass → 0.77 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/x402-bazaar-mcp@0.3.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 118 packages
Packages resolved 118
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~202 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
call_x402_service ~104

Call any x402 Bazaar service by id with its parameters. Pays via the configured mode (free daily call / prepaid credit token / wallet). Use list_x402_services to see ids and inputs. Example: service="token-risk", params={ "address": "0x…" }.

NameTypeReqDescription
paramsobject–The service's input parameters as an object.
servicestringyesThe service id, e.g. "token-risk" or "price-impact".

No output schema declared.

No examples provided.

list_x402_services ~98

List every service in the x402 Bazaar catalog (id, name, price, category, tagline). Call this first to discover what is available, then call a service by its own tool or via call_x402_service. Free, no payment.

NameTypeReqDescription
categorystring–Filter by category (e.g. Onchain, Markets, AI).
querystring–Case-insensitive substring to filter by id / name / tagline.

No output schema declared.

No examples provided.

Install

How do I install the io.github.sukrutkrdg/x402-bazaar-mcp server?

io.github.sukrutkrdg/x402-bazaar-mcp runs locally as an npm package, launched with npx -y x402-bazaar-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · x402-bazaar-mcp

# add to Claude Code
claude mcp add sukrutkrdg-x402-bazaar-mcp -- npx -y x402-bazaar-mcp
Common questions

What is the io.github.sukrutkrdg/x402-bazaar-mcp server?

io.github.sukrutkrdg/x402-bazaar-mcp is listed in the public MCP registry as io.github.sukrutkrdg/x402-bazaar-mcp. Check, then act, on Base and NEAR: token-safety gates, then swaps at the best price, over x402. This page covers its npm package (x402-bazaar-mcp).

Is the io.github.sukrutkrdg/x402-bazaar-mcp server safe to use?

io.github.sukrutkrdg/x402-bazaar-mcp scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.sukrutkrdg/x402-bazaar-mcp server expose?

io.github.sukrutkrdg/x402-bazaar-mcp exposes 2 tools: list_x402_services, call_x402_service. Their descriptions and schemas cost roughly 202 tokens of context every time the server is loaded.

Is the io.github.sukrutkrdg/x402-bazaar-mcp server still maintained?

io.github.sukrutkrdg/x402-bazaar-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.sukrutkrdg/x402-bazaar-mcp server under?

io.github.sukrutkrdg/x402-bazaar-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.