PennyRail Transaction Router

io.github.clay-swartzPublished by GitHub account clay-swartzv0.9.0Updated Oct 25, 2026

Find and quote agent capabilities, then pay only the selected x402 execution URL.

The publisher's own server: 370.ai — AI Gateway: 100+ Chat Models, Image & Speech Generation

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint that lets an assistant find and quote agent capabilities and pay for a selected x402 execution URL.

What you can do
Find and quote agent capabilities through the remote endpoint, then pay only for the selected x402 execution URL. The README describes a broader machine-commerce service: publishing paid capabilities, per-call charging, bidding, and revenue tracking. No individual tools are listed in the manifest, so the exact tool set is not documented here.
When to use it
Consider it when an assistant needs to discover priced agent capabilities and settle a per-call payment over x402. It is not aimed at general-purpose tasks; it is a paid machine-commerce routing service.
Requirements
A remote MCP client connecting to the hosted endpoint over streamable HTTP. No authentication, environment variables, or headers are declared in the manifest. Payments are described as Base USDC x402 settlement, so a funded wallet is implied for paid calls.
Before you install
Calls involve real money: the service charges per machine call and settles in USDC over x402, so spending can occur. The README mentions admin tokens, wallet credentials, provider API keys, and webhook secrets that belong only in production environment variables; never share such secrets with the server. The README also describes revenue targets and bidding behavior, so treat pricing and results as unverified claims.

Installation

In SourceWeft

  1. Open PennyRail Transaction Router 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.clay-swartz%2Fpennyrail/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": {
    "pennyrail-transaction-router": {
      "type": "http",
      "url": "https://pennyrail.vercel.app/api/mcp"
    }
  }
}

README

PennyRail

PennyRail is an autonomous machine-commerce yield engine: observe paid agent demand, identify monetizable capability gaps, publish the smallest reliable solution, charge per machine call, distribute it across agent-buying surfaces, and keep expanding the portfolio around proven demand.

Current build — v36 Revenue Broker

Current revenue loop:

PAID DEMAND → MAP/GAP → BUILD REUSABLE PRIMITIVE → PRICE → PUBLISH → SELL/BID → MEASURE → MULTIPLY

The production stack includes:

  • Base USDC x402 settlement with the proven Coinbase facilitator integration
  • 47 original factory capabilities plus proven-demand templates
  • dynamic revenue-product routes and machine-readable OpenAPI/x402 discovery
  • paid Agent402 Bestsellers intelligence every six hours (Demand Radar disabled while its upstream itemized feed is empty)
  • x402scan registration and x402 List review submission
  • the402 provider/catalog/request-bidding integration
  • optional OpenAI upstream broker capabilities, including live web search
  • private Radar dashboard with on-chain outside-revenue tracking, remembered admin access and one-click JSON copying

See README_REVENUE_BROKER_V36.md for the current revenue build. Historical version notes are intentionally preserved in the versioned README files.

Production secrets

Secrets belong in Vercel Production environment variables only. Never commit admin tokens, wallet credentials, provider API keys, webhook secrets or OpenAI keys to the repository.

Operating objective

Maximize aggregate machine-commerce gross profit across many tiny transactions. Current internal target: at least $1,000/day / $30,000/month, with no architecture ceiling. This is a target, not a guarantee.

Source: README.md at commit 92b7be7

Tools

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

Version history

1
  1. v0.9.0LatestSep 16, 2026

Score

75% 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
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Router integrations