Stinkyboy Bodega

io.github.noahmchughPublished by GitHub account noahmchughv1.0.1Updated Oct 24, 2026

One integration, one wallet. Thousands of callable tools, paid per call in USDC via x402.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

A remote MCP endpoint that offers a large catalog of callable tools, each paid per call in USDC through x402.

What you can do
Access a large catalog of callable tools through a single integration, according to the provider's description. Pay for each tool call individually in USDC via x402 rather than through a subscription. The manifest lists no individual tools, so the specific capabilities are not documented here.
When to use it
Consider it when you want many different tool capabilities behind one MCP connection and are willing to pay per call in USDC. It is a poor fit if you need a documented tool list, free usage, or a local package.
Requirements
A remote MCP client connecting to the provider's streamable HTTP endpoint. A wallet able to pay in USDC via x402 is implied by the description. No authentication, environment variables, or headers are declared in the manifest.
Before you install
Every tool call is described as paid in USDC, so usage spends real money and costs should be checked before connecting an assistant. Payment goes through x402, which involves a wallet; the manifest declares no authentication details, so how the wallet is authorized is unclear. No tool list is published, so what each call does and what data it receives cannot be verified in advance.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.noahmchugh%2Fstinkyboy-bodega/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "stinkyboy-bodega": {
      "type": "http",
      "url": "https://mcp.stinkyboy.co/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1LatestSep 24, 2026

Score

60% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 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.