nostr

Manage Nostr channel access — approve pairings, edit allowlists, set policy. Use when the user asks to pair, approve someone, check who's allowed, or change access policy for the Nostr channel.

Encode and decode NIP-19 bech32 Nostr entities (note1, npub1, nevent1, nprofile1, naddr1). Use when the user provides a bech32 string and wants to extract the event ID, pubkey, or relay hints, or wants to encode a hex ID/pubkey into a bech32 string.

Set up the Nostr channel — save the nsec private key, manage relays, and configure subscribed event kinds. Use when the user wants to configure Nostr, add/remove relays, or change subscribed kinds.

Fetch a specific Nostr event by ID or filter using the fetch_event tool. Use when the user wants to look up a note, DM, profile, or any Nostr event by its ID (hex or note1/nevent format), or by author/kind filter.

Mine a Nostr keypair with a vanity pubkey prefix or target difficulty using rana. Use when the user wants to generate a Nostr public key that starts with specific hex characters, a specific npub prefix/suffix, or meets a minimum proof-of-work difficulty. Requires rana installed in PATH.

Interact with users over the Nostr decentralized protocol. Use when handling inbound Nostr DMs, sending replies, publishing notes, fetching events, or checking relay status. Inbound messages arrive as channel notifications.

View or update the Nostr profile (kind:0 metadata). Caches identity info in profile.json. Use when the user wants to set their Nostr name, bio, avatar, NIP-05, or lightning address.

React to a Nostr event with a NIP-25 kind:7 reaction — like (+), dislike (-), or any emoji. Use when the user wants to react to, like, or emoji-respond to a Nostr note or event.

Manages the kind:10002 relay list for this Nostr identity. Cached locally at

Verify a Nostr event — check schema validity, ID hash, and Schnorr signature. Use when the user wants to validate a Nostr event, check if an event is authentic, or debug a malformed event.