Cinderwright Api
Discover and route agent payments across x402, MPP, and L402/Lightning from one MCP hub instead of wiring each protocol separately.
Overview
Cinderwright API MCP is a Build-phase MCP server that acts as a cross-protocol agent payments hub indexing 1551 services across x402, MPP, and L402/Lightning.
What is this MCP server?
- 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
- 1551 services indexed in the payments hub
- MCP server version 1.1.1; npm identifier cinderwright-mcp-server
Community signal: 1 GitHub stars.
What problem does it solve?
Agent builders hit a fragmented paid-API landscape and waste time matching services to the right micropayment or Lightning protocol without a unified catalog.
Who is it for?
Solo developers building paid agent tools or API marketplaces who need protocol-agnostic payment discovery early in integration design.
Skip if: Teams that only need a single Stripe checkout for humans or have no agent-to-service micropayment requirements.
What do I get? / Deliverables
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
Recommended MCP Servers
Journey fit
Monetized and API-backed agents are assembled in Build when integrations for billing and external paid services must land before ship. Integrations subphase covers payment rails and third-party service catalogs that agents invoke during product construction.
How it compares
Payments and service-index MCP hub, not a single-domain data vault or a standalone Claude skill file.
Common Questions / FAQ
Who is cinderwright-api for?
Indie agent builders 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.