402 Mcp
Let your agent discover Lightning-gated HTTP APIs, pay per request in sats, and call them without you manually funding each tool.
Overview
402-mcp is a MCP server for the Build phase that enables agents to autonomously pay for and call Lightning-gated APIs.
What is this MCP server?
- 402-mcp v3.15.2 stdio npm server for Lightning-gated APIs
- Agents discover, pay for, and consume paid endpoints autonomously
- NWC_URI secret plus optional MAX_AUTO_PAY_SATS cap per request
- Repository: github.com/forgesworn/402-mcp
- Server version 3.15.2
- npm identifier: 402-mcp
- Required secret env: NWC_URI
What problem does it solve?
Agents hit HTTP 402 paywalls on useful APIs and stall because there is no standard MCP path to fund Lightning invoices within safe limits.
Who is it for?
Builders shipping agent workflows that consume Lightning-monetized APIs and want capped autonomous spend via NWC.
Skip if: Teams on card-only SaaS billing with no Lightning wallet, or anyone uncomfortable giving an agent any auto-pay capability.
What do I get? / Deliverables
With NWC configured, your agent can discover gated APIs, auto-pay within MAX_AUTO_PAY_SATS, and return paid API data in the session.
- Agent-callable paid API access via Lightning settlement
- Configured spend ceiling via MAX_AUTO_PAY_SATS environment variable
Recommended MCP Servers
Journey fit
Paid API consumption wiring happens in Build integrations when you connect agents to external services—not in launch marketing or grow analytics. integrations holds MCP servers that broker third-party APIs; 402-mcp adds micropayment discovery and autonomous Lightning settlement.
How it compares
Lightning micropayment API client MCP, not a Stripe subscription or invoice dashboard integration.
Common Questions / FAQ
Who is dev.forgesworn/402-mcp for?
Solo builders and agent authors who use Lightning-gated HTTP APIs and want MCP-driven discovery and payment without manual invoice approval each time.
When should I use dev.forgesworn/402-mcp?
Use it during Build when integrating paid external APIs that return HTTP 402 and you are ready to configure NWC_URI and a sats spend cap.
How do I add dev.forgesworn/402-mcp to my agent?
Register stdio MCP with npm package 402-mcp (v3.15.2), set secret NWC_URI for your wallet connect URI, and optionally MAX_AUTO_PAY_SATS in the server environment.