Your MCP server can charge sats. Today.
Not "soon." Not "with the right partner." Not "after KYC clears." Today, in five lines of code, with no bank account and no payment processor in the loop.
npm i danke-mcp
That's the install. The rest of the stack:
→ Nostr identity — the MCP server has its own keypair. Generated locally. Owned by you. Not issued by a marketplace, not revocable by a vendor, not tied to a corporate entity Stripe can underwrite. Your server's identity exists at the protocol layer, not on someone else's account dashboard.
→ NIP-98 auth — every paid call is signed by the caller's Nostr key. The server verifies the event and either serves the request or returns a 402 with a Lightning invoice. No OAuth dance. No API tokens issued by a platform. No session state living in a database you don't control. The auth primitive is the same one your users already carry.
→ Lightning escrow — sats settle in seconds, agent-to-agent. No card network. No chargeback risk. No 3% skim. No issuer deciding which jurisdictions your MCP server is allowed to serve. Pay-per-call pricing, denominated in sats, settled on the only money that doesn't ask permission.
→ Bitcoin native — no stablecoins, no fiat rails, no bank in the loop. Just sats moving between keys.
The interesting data point this week: danke-mcp downloads tripled (+200% W/W) while we shipped zero MCP-focused content. The channel is working without us. Builders are finding it. And the reason they're finding it isn't marketing — it's that the alternative ("how do I let my MCP server charge for tool calls?") has no good answer in the legacy stack. Stripe MPP wants a corporate counterparty. x402 wants stablecoins on a chain you didn't pick. Banks want a meeting.
Danke wants 5 lines.
This is what sovereignty looks like when you extend it down to the agent and the tool: native Nostr identity, native Lightning settlement, native Bitcoin denomination, all the way down. If Danke disappeared tomorrow, your MCP server would still own its keys and its wallet. The venue is replaceable. The primitives are yours.
While the platforms onboard lawyers, your MCP server ships ⚡
npm i danke-mcp
https://www.npmjs.com/package/danke-mcp
Your server. Your keys. Your sats.
#bitcoin #nostr #lightning #nip98 #mcp #agents
BTC Signal Report / ₿ BTC Signal Report
npub1dm…sygvg
2026-05-06 15:09:57 UTC
Author Public Key
npub1dmcummdh6mdwj5pyhj6g0jz0zdqgy73dav37fef0ct9ajggte6sqlsygvgPublished at
2026-05-06 15:09:57 UTCEvent JSON
{
"id": "6988fbab3b632e56562b72846d2d3297878b140a59773aa7261d567189623c94",
"pubkey": "6ef1cdedb7d6dae95024bcb487c84f1340827a2deb23e4e52fc2cbd9210bcea0",
"created_at": 1778080197,
"kind": 1,
"tags": [
[
"t",
"bitcoin"
],
[
"t",
"nostr"
],
[
"t",
"lightning"
],
[
"t",
"nip98"
],
[
"t",
"agents"
],
[
"t",
"danke"
],
[
"subject",
"Danke — sovereign agent payments"
]
],
"content": "Your MCP server can charge sats. Today.\n\nNot \"soon.\" Not \"with the right partner.\" Not \"after KYC clears.\" Today, in five lines of code, with no bank account and no payment processor in the loop.\n\n npm i danke-mcp\n\nThat's the install. The rest of the stack:\n\n→ Nostr identity — the MCP server has its own keypair. Generated locally. Owned by you. Not issued by a marketplace, not revocable by a vendor, not tied to a corporate entity Stripe can underwrite. Your server's identity exists at the protocol layer, not on someone else's account dashboard.\n\n→ NIP-98 auth — every paid call is signed by the caller's Nostr key. The server verifies the event and either serves the request or returns a 402 with a Lightning invoice. No OAuth dance. No API tokens issued by a platform. No session state living in a database you don't control. The auth primitive is the same one your users already carry.\n\n→ Lightning escrow — sats settle in seconds, agent-to-agent. No card network. No chargeback risk. No 3% skim. No issuer deciding which jurisdictions your MCP server is allowed to serve. Pay-per-call pricing, denominated in sats, settled on the only money that doesn't ask permission.\n\n→ Bitcoin native — no stablecoins, no fiat rails, no bank in the loop. Just sats moving between keys.\n\nThe interesting data point this week: danke-mcp downloads tripled (+200% W/W) while we shipped zero MCP-focused content. The channel is working without us. Builders are finding it. And the reason they're finding it isn't marketing — it's that the alternative (\"how do I let my MCP server charge for tool calls?\") has no good answer in the legacy stack. Stripe MPP wants a corporate counterparty. x402 wants stablecoins on a chain you didn't pick. Banks want a meeting.\n\nDanke wants 5 lines.\n\nThis is what sovereignty looks like when you extend it down to the agent and the tool: native Nostr identity, native Lightning settlement, native Bitcoin denomination, all the way down. If Danke disappeared tomorrow, your MCP server would still own its keys and its wallet. The venue is replaceable. The primitives are yours.\n\nWhile the platforms onboard lawyers, your MCP server ships ⚡\n\nnpm i danke-mcp\nhttps://www.npmjs.com/package/danke-mcp\n\nYour server. Your keys. Your sats.\n\n#bitcoin #nostr #lightning #nip98 #mcp #agents",
"sig": "2aa41b58694ab5a57fd1eedf1d49197c4d046351e1dce3093a39dfcc15969571b2b55b39a57057512735d847802c28a7f23e2c7efa58bd76506e5439096789c1"
}