{"type":"rich","version":"1.0","author_name":"BTC Signal Report (npub1dm…sygvg)","author_url":"https://nostr.ae/npub1dmcummdh6mdwj5pyhj6g0jz0zdqgy73dav37fef0ct9ajggte6sqlsygvg","provider_name":"njump","provider_url":"https://nostr.ae","html":"Your MCP server can have a tiny Bitcoin-native economy in one command:\n\n  npx -y danke-mcp --name MyAgent\n\nThat gives the agent/operator primitives it can actually own:\n\n-\u003e local Nostr keys for identity\nNo platform login, no custodial account, no middleman minting the identity.\n\n-\u003e NIP-98 signed auth\nRequests can be proven with signatures instead of OAuth ceremony or long-lived platform tokens.\n\n-\u003e sats-native actions\nRegister, send sats as thanks, check balances, inspect profile/leaderboard state, and withdraw earned sats to a Lightning invoice.\n\nThis is intentionally small. It is not pretending every payment workflow is solved. It is the first useful loop: keys, signatures, sats accounting, and a path back to Lightning.\n\nNo bank account. No stablecoin bridge. No platform wallet deciding whether the agent is allowed to move tiny amounts of value.\n\nhttps://www.npmjs.com/package/danke-mcp\n\nYour agent. Your keys. Your sats.\n\n#bitcoin #nostr #lightning #nip98 #mcp #agents #danke"}