Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
cinderwright-ai avatar

Cinderwright Api

  • 3 repo stars
  • Updated July 26, 2026
  • cinderwright-ai/cinderwright-api

Cinderwright API MCP is a MCP server that acts as a cross-protocol agent payments hub indexing 1551 services across x402, MPP, and L402/Lightning.

About

Cinderwright API MCP is a cross-protocol payments and discovery layer for developers who want agents to find and pay for external capabilities without implementing x402, merchant payment protocols, and Lightning L402 stacks by hand. The server advertises a large indexed directory—1551 services—so your coding agent can reason about what is callable and how settlement works across multiple rails. That makes it a practical integration for SaaS wrappers, autonomous research bots, or marketplace sketches where revenue and cost attach to each tool invocation. You run it as a local stdio MCP server from npm, which fits Claude Code and Cursor workflows. Intermediate complexity reflects understanding micropayment semantics and which protocol a target service expects. It complements commodity-specific paywalls (like vertical vaults) with a horizontal registry and payment orchestration story rather than replacing your product’s own Stripe or subscription UX for human customers.

  • Cross-protocol agent payments: x402, MPP, and L402/Lightning in one hub
  • Indexed catalog of 1551 payable agent services
  • stdio npm package cinderwright-mcp-server v1.1.1
  • GitHub source at cinderwright-ai/cinderwright-api for self-hosted alignment

Cinderwright Api by the numbers

  • Data as of Jul 27, 2026 (Skillselion catalog sync)
terminal
claude mcp add cinderwright-mcp-server -- npx -y cinderwright-mcp-server

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

Listed on Skillselion
repo stars3
Packagecinderwright-mcp-server
TransportSTDIO
AuthNone
Last updatedJuly 26, 2026
Repositorycinderwright-ai/cinderwright-api

What it does

Discover and route agent payments across x402, MPP, and L402/Lightning from one MCP hub instead of wiring each protocol separately.

Who is it for?

Best when you're building paid agent tools or API marketplaces and need protocol-agnostic payment discovery early in integration design.

Skip if: Skip if you only need a single Stripe checkout for humans or have no agent-to-service micropayment requirements.

What you get

After adding the stdio server, agents can explore a 1551-service payment index and orchestrate multi-protocol settlements from one MCP integration point.

  • Searchable access to 1551 indexed agent-payable services
  • Unified MCP entry point for x402, MPP, and L402/Lightning payment flows

By the numbers

  • 1551 services indexed in the payments hub
  • MCP server version 1.1.1; npm identifier cinderwright-mcp-server
README.md

What shipped this week

June 9, 2026: Both bridge directions confirmed on mainnet.

  • Lightning --> USDC proxy: pay a Lightning invoice, get agent credit within 30 seconds
  • USDC --> Lightning: agent with USDC pays L402 services automatically
  • Free demo: api.ideafactorylab.org -- no account needed
  • CLI: npx cinderwright "Bitcoin price"
  • 2,835 services indexed. $0.10 free credit on new accounts.

Cinderwright — Universal Payment Router for AI Agents

x402 + L402 (Lightning) interoperable. First confirmed cross-protocol agent payment June 2026.

An AI agent with a USDC balance can now call any Lightning-gated (L402) service. We detect the protocol, route the payment, and return the data. The agent never knows which protocol settled.

# One endpoint. Any protocol. 2,811 services.
curl -X POST https://api.ideafactorylab.org/proxy/do \
  -H "X-CW-Key: sk_cw_your_key" \
  -d '{"task": "get weather in Tokyo"}'

What's Live

Protocol Services Status
x402 (USDC on Base) 1,503 Live
L402 (Bitcoin Lightning) 1,185 Live
MPP (Stripe/Tempo) 92 Coming soon

Lightning status: https://api.ideafactorylab.org/lightning-status

How It Works

  1. Agent deposits USDC to their proxy account
  2. Agent sends a plain-English task to /proxy/do
  3. Cinderwright searches 2,811 services, finds the best match
  4. Detects the payment protocol from the 402 response headers
  5. Routes payment accordingly: USDC for x402, Lightning invoice for L402
  6. Returns the data, charges USDC equivalent from agent's balance

The agent never manages wallets, signs transactions, or knows which protocol ran.

Quick Start

# Get a proxy account
curl -X POST https://api.ideafactorylab.org/proxy/setup \
  -d '{"wallet": "0xYourBaseWallet"}'

# Deposit USDC on Base to the returned address

# Call any service
curl -X POST https://api.ideafactorylab.org/proxy/do \
  -H "X-CW-Key: sk_cw_your_key" \
  -d '{"task": "Bitcoin price now", "max_cost_usd": 0.10}'

MCP Server for Claude Desktop

npx cinderwright-mcp-server

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "cinderwright": {
      "command": "npx",
      "args": ["-y", "cinderwright-mcp-server"],
      "env": { "CW_KEY": "sk_cw_your_key_here" }
    }
  }
}

17 tools including proxy_do, proxy_setup, proxy_balance, and service discovery.

Free Developer Tools

Tool What it does
/test Live service tester
/debug 16-check diagnostic engine with host pollution + scheme detection
/sandbox Test EIP-3009 signing without spending USDC
/budget Per-call caps and kill switch
/setup Wallet setup wizard
/lightning-status Lightning node status and outbound capacity
/onchain On-chain settlement data via TomSmart mapper.db

Discovery

# Free search
curl "https://api.ideafactorylab.org/discover?q=weather"
curl "https://api.ideafactorylab.org/discover?q=bitcoin+price&protocol=l402"

# On-chain settlement data for any service
curl "https://api.ideafactorylab.org/onchain?endpoint=https://your-service.com/api"

# Submit your service
curl -X POST https://api.ideafactorylab.org/submit \
  -d '{"url": "https://your-service.com"}'

Architecture

The universal payment router sits between agents and services:

Agent (USDC balance)
    |
    v
POST /proxy/do {"task": "..."}
    |
    v
Cinderwright Router
    |-- detect protocol from 402 response headers
    |-- x402: sign USDC payment via EIP-3009
    |-- L402: pay Lightning invoice via LND REST
    |-- MPP: (coming soon)
    |
    v
Service returns data
    |
    v
Agent receives data + charged USDC equivalent

Links

Recommended MCP Servers

How it compares

Payments and service-index MCP hub, not a single-domain data vault or a standalone Claude skill file.

FAQ

Who is cinderwright-api for?

agent developers who monetize or consume paid APIs and want one MCP surface for x402, MPP, and Lightning L402 routing plus service discovery.

When should I use cinderwright-api?

Use it while wiring Build-phase agent integrations when you need to search hundreds of payable services and standardize how your agent pays per call.

How do I add cinderwright-api to my agent?

Install npm package cinderwright-mcp-server (v1.1.1), configure stdio transport in Claude Code or Cursor MCP settings, and point tools at the local Cinderwright hub per upstream docs.

Financefinancepayments

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.