Bazaar Mcp

io.github.opspawnPublished by GitHub account opspawnv1.0.2Updated Oct 30, 2026

x402 micropayment-powered developer tools: screenshots, AI analysis, PDFs, code scanning

Overview

AI-generated overview

Local MCP server that gives an assistant x402 micropayment-powered developer tools such as screenshots, AI analysis, PDFs and code scanning.

What you can do
  • Capture screenshots of web pages or other targets through the Bazaar gateway.
  • Run AI analysis on supplied content.
  • Produce PDFs.
  • Scan code.
  • All of these are paid x402 micropayment services reached through a configurable gateway URL.
When to use it
Useful when you want an assistant to take screenshots, generate PDFs, scan code or run AI analysis without wiring up separate services, and you are willing to pay per request through x402 micropayments.
Requirements
Runs as a local stdio process, installed from the npm package bazaar-mcp (Node.js). Needs network access to the x402 Bazaar gateway; BAZAAR_GATEWAY_URL sets the base URL and defaults to a hosted gateway. An x402 payment token is supplied via X402_PAYMENT_TOKEN.
Before you install
Requests are paid through x402 micropayments, so usage can spend money. The X402_PAYMENT_TOKEN secret is sent to the configured gateway, and pointing BAZAAR_GATEWAY_URL at a different host sends that token and your content there. Content submitted for screenshots, analysis, PDFs or code scanning is processed by the remote gateway.

Installation

In SourceWeft

  1. Open Bazaar Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.