io.github.clay-swartz/pennyrail (MCP Server)

PennyRail (io.github.clay-swartz/pennyrail) is an MCP server described as a “machine-commerce yield engine.” It finds and quotes agent capabilities, then pays only the selected x402 execution URL. The provided description also frames a loop of observing paid agent demand and building monetizable solutions.

🛠️ Key Features

Find and quote agent capabilities
Pay only the selected x402 execution URL
Tool count: 2 (as provided)
Current build: v36 Revenue Broker (per excerpt)

🚀 Use Cases

Turning “paid agent demand” into “monetizable capability gaps”
Publishing and selling/bidding solutions
Measuring outcomes and multiplying results

⚡ Developer Benefits

Uses a defined revenue loop: PAID DEMAND → MAP/GAP → BUILD REUSABLE PRIMITIVE → PRICE → PUBLISH → SELL/BID → MEASURE → MULTIPLY
Base USDC x402 settlement with “proven Coinbase facilitator integration” (per excerpt)

⚠️ Limitations

The excerpt truncates after “47 original factory capab,” so details of the full implementation are not provided.

{ "type": "object", "properties": { "intent": { "type": "string", "minLength": 1, "description": "What the agent needs, in natural language." }, "limit": { "description": "Maximum candidates to return.", "type": "integer", "minimum": 1, "maximum": 20 } }, "required": [ "intent" ], "$schema": "https://json-schema.org/draft/2020-12/schema" }

{ "type": "object", "properties": { "productId": { "description": "Exact productId returned by pennyrail_find.", "type": "string", "minLength": 1 }, "intent": { "description": "Natural-language need when productId is not known.", "type": "string", "minLength": 1 } }, "$schema": "https://json-schema.org/draft/2020-12/schema" }

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.

Install

Tools (2)

pennyrail_findpennyrail_quote

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://pennyrail.vercel.app/api/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "pennyrail": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://pennyrail.vercel.app/api/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

PennyRail Transaction Router

io.github.clay-swartz/pennyrail (MCP Server)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

pennyrail_find

pennyrail_quote

PennyRail

Current build — v36 Revenue Broker

Production secrets

Operating objective

Install

Remote endpoint

Related servers

intent	string	required	What the agent needs, in natural language.
limit	integer	optional	Maximum candidates to return.

productId	string	optional	Exact productId returned by pennyrail_find.
intent	string	optional	Natural-language need when productId is not known.