stinkyboy

io.github.noahmchughPublished by GitHub account noahmchughv1.0.0Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableFinanceAI & ML

Overview

AI-generated overview

Remote MCP endpoint that gives an assistant access to thousands 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.
  • Pay for individual tool calls in USDC via the x402 payment protocol.
  • Use one wallet connection instead of separate integrations per tool.
  • The listing names no individual tools, so the exact capabilities are not documented here.
When to use it
Consider it when you want a single endpoint that fronts many third-party tools and you are prepared to pay per call in USDC rather than manage separate integrations.
Requirements
A remote MCP client connecting to the hosted endpoint over streamable HTTP. A crypto wallet holding USDC to pay per call via x402. No API keys, environment variables or headers are declared.
Before you install
Every tool call costs USDC, so usage spends real money and costs may accumulate quickly. The server is tied to a wallet, so treat wallet access as sensitive. The listing does not document which tools exist, what they do, or what data they send to third parties, so verify before relying on it.

Installation

In SourceWeft

  1. Open stinkyboy 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/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": {
      "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.0LatestSep 23, 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 daysRequired25 pts

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

  • Auth declaredRequired10 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.