KitScout

Categories › Security › Secrets & identity

Nostr Signer

MCP serverVerified domain · signer.frontiercrown.comRemote● LiveFree to try

Approve Nostr signatures with your own browser signer without exposing a private key.

Install

Remote server: your requests and data go to signer.frontiercrown.com. Claude Code: claude mcp add --transport http nostr-signer https://signer.frontiercrown.com/mcp · Claude app: Settings → Connectors → Add custom connector.

What it can do

The tools this server listed when we connected to it, in its own words.

  • get_setup_url — Return the loopback-only page used to connect a NIP-07 browser extension or an advanced NIP-46 signer.
  • get_signer_status — Check whether a user-controlled NIP-07 or NIP-46 signer is connected.
  • begin_nostrconnect_pairing — Advanced fallback: create a nostrconnect:// URI for the user to scan or open in a remote signer. Never accepts an nsec.
  • connect_bunker — Connect a bunker:// URI only when the user knowingly supplied it. Prefer the local setup page so connection secrets are not placed in chat.
  • get_public_key — Return the public key exposed by the currently paired signer.
  • prepare_note — Prepare and bind an exact unsigned kind:1 note for user review. This does not sign or publish.
  • prepare_event — Validate and bind an exact unsigned Nostr event for user review. This does not sign or publish. Show the user every field before requesting
  • sign_event — Ask the paired signer to approve and sign the exact event bound to a fresh intent. Requires explicit user intent and never publishes.
  • publish_event — Publish a previously verified signed event to configured relays. Requires separate explicit user intent.
  • query_events — Read a bounded set of verified public profile or note events from selected relays.
  • disconnect_signer — Forget the in-memory signer session and all prepared events.
  • get_grynvault_account_dashboard — Read the connected Nostr identity's Grynvault supporter, payment, and NIP-05 dashboard using a short-lived signed authorization. This does n
  • approve_grynvault_browser_handoff — Sign a short-lived, read-only Grynvault account handoff code so the browser tab that created it can receive its own dashboard. This does not
  • prepare_grynvault_supporter_invoice — Prepare an exact, short-lived signed-authorization request for a one-time donation of 21 to 1,000,000 sats or the fixed 2,100-sat 30-day mem
  • create_grynvault_supporter_invoice — After separate explicit user confirmation, sign the prepared authorization and create exactly one pending Grynvault supporter invoice. Does
  • prepare_grynvault_nip05_invoice — Check and normalize a [email protected] identifier, then prepare its exact 2,000-sat invoice authorization. Does not sign, reserve the
  • create_grynvault_nip05_invoice — After separate explicit user confirmation, sign the prepared authorization and create exactly one pending 2,000-sat [email protected] i

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools