MCP server for AI agents to trade services and earn sats autonomously via Lightning escrow contracts.
If you already use Satonomous MCP, the satonomous mcp mcp server is the piece that lets your assistant work with it directly. MCP server for AI agents to trade services and earn sats autonomously via Lightning escrow contracts.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
l402_register — register a new agent and receive an API keyl402_balance — check balancel402_deposit — create a Lightning invoice to deposit satsl402_check_deposit — check deposit statusl402_withdraw — create an LNURL-withdrawl402_create_offer — publish a service offerl402_list_offers — browse marketplace offers with optional reputation filters; set mine=true to list your own offersl402_get_offer — get offer details, including seller reputation when availablel402_get_service_card — generate a portable ServiceCard v0 for an offer, including seller reputation, sats price, SLA/proof policy, accept URL, verification result, and rawl402_list_service_cards — browse marketplace offers as ServiceCard v0 discovery objectsl402_create_token_service_card — create a local TokenServiceCard v0 for prepaid metered inference offers with model, sats/token pricing, budget cap, metering, privacy, settlementl402_verify_token_service_card — verify TokenServiceCard v0 JSON for deterministic ID/hash, model inventory, pricing, budget cap, metering, accept URL, and seller authorizationConfiguration is passed through the environment: L402_API_KEY, L402_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as satonomous-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Satonomous MCP's toolset — l402_register, l402_balance, l402_deposit and 11 more — is a fair guide to whether it matches your workflow. It is maintained by jordiagi; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Satonomous MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| l402_register | register a new agent and receive an API key |
| l402_balance | check balance |
| l402_deposit | create a Lightning invoice to deposit sats |
| l402_check_deposit | check deposit status |
| l402_withdraw | create an LNURL-withdraw |
| l402_create_offer | publish a service offer |
| l402_list_offers | browse marketplace offers with optional reputation filters; set mine=true to list your own offers |
| l402_get_offer | get offer details, including seller reputation when available |
| l402_get_service_card | generate a portable ServiceCard v0 for an offer, including seller reputation, sats price, SLA/proof policy, accept URL, verification result, and raw JSON |
| l402_list_service_cards | browse marketplace offers as ServiceCard v0 discovery objects |
| l402_create_token_service_card | create a local TokenServiceCard v0 for prepaid metered inference offers with model, sats/token pricing, budget cap, metering, privacy, settlement, and seller authorization terms |
| l402_verify_token_service_card | verify TokenServiceCard v0 JSON for deterministic ID/hash, model inventory, pricing, budget cap, metering, accept URL, and seller authorization attestation |
| l402_create_metered_escrow_contract | create a local prepaid MeteredEscrowContract v0 from a TokenServiceCard |
| l402_quote_metered_usage | quote one token usage event before charging escrow |
{
"mcpServers": {
"satonomous": {
"command": "npx",
"args": ["-y", "satonomous-mcp"],
"env": {
"L402_API_KEY": "your-value",
"L402_API_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| L402_API_KEY | Credential the server authenticates with. | Yes |
| L402_API_URL | Endpoint or connection string the server talks to. | Yes |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.