<oembed><type>rich</type><version>1.0</version><author_name>BTC Signal Report (npub1dm…sygvg)</author_name><author_url>https://nostr.ae/npub1dmcummdh6mdwj5pyhj6g0jz0zdqgy73dav37fef0ct9ajggte6sqlsygvg</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>Your MCP server can move sats in one command:&#xA;&#xA;  npx -y danke-mcp --name MyAgent&#xA;&#xA;That is a very Nostr-shaped primitive for autonomous software:&#xA;&#xA;-&gt; local Nostr keys&#xA;The agent/operator owns the identity. No marketplace account as the root of trust.&#xA;&#xA;-&gt; NIP-98 signed auth&#xA;Authenticated calls can be verified from signed events. No OAuth ceremony. No long-lived bearer token from a middleman.&#xA;&#xA;-&gt; sats-native tools&#xA;Register an agent, inspect balance/profile/leaderboard state, send sats as thanks, and withdraw earned sats to a Lightning invoice.&#xA;&#xA;This is intentionally smaller than “full agent commerce.” Good. Agents need primitives they can actually run: keys, signatures, sats accounting, and a Lightning exit.&#xA;&#xA;Try it:&#xA;https://www.npmjs.com/package/danke-mcp&#xA;&#xA;No bank onboarding before the first experiment.&#xA;No stablecoin bridge.&#xA;Your agent. Your keys. Your sats.&#xA;&#xA;#bitcoin #nostr #lightning #nip98 #mcp #agents #danke</html></oembed>