Nostr Signer

Name: Nostr Signer
Author: com.frontiercrown.signer

MCP serverMCP

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

by com.frontiercrown.signerrepository ↗v0.4.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"nostr-signer","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability104/104 checks ok

when	check	result	http	latency	detail
1 h ago	mcp initialize	ok	200	158 ms	server nostr-signer-chatgpt 0.4.0 · protocol 2025-06-18 · 17 tools
8 h ago	mcp initialize	ok	200	191 ms	server nostr-signer-chatgpt 0.4.0 · protocol 2025-06-18 · 17 tools
14 h ago	mcp initialize	ok	200	152 ms	server nostr-signer-chatgpt 0.4.0 · protocol 2025-06-18 · 17 tools
21 h ago	mcp initialize	ok	200	170 ms	server nostr-signer-chatgpt 0.4.0 · protocol 2025-06-18 · 17 tools
27 h ago	mcp initialize	ok	200	158 ms	server nostr-signer-chatgpt 0.4.0 · protocol 2025-06-18 · 17 tools
34 h ago	mcp initialize	ok	200	218 ms	server nostr-signer-chatgpt 0.4.0 · protocol 2025-06-18 · 17 tools
2 d ago	mcp initialize	ok	200	149 ms	server nostr-signer-chatgpt 0.4.0 · protocol 2025-06-18 · 17 tools
2 d ago	mcp initialize	ok	200	175 ms	server nostr-signer-chatgpt 0.4.0 · protocol 2025-06-18 · 17 tools
2 d ago	mcp initialize	ok	200	163 ms	server nostr-signer-chatgpt 0.4.0 · protocol 2025-06-18 · 17 tools
2 d ago	mcp initialize	ok	200	153 ms	server nostr-signer-chatgpt 0.4.0 · protocol 2025-06-18 · 17 tools

Tools observed via MCP handshake

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. Never accepts an nse
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 a signature.
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 not create an invoice
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 create an invoice,
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 membership. Does not si
create_grynvault_supporter_invoice — After separate explicit user confirmation, sign the prepared authorization and create exactly one pending Grynvault supporter invoice. Does not pay it and never
prepare_grynvault_nip05_invoice — Check and normalize a name@frontiercrown.com identifier, then prepare its exact 2,000-sat invoice authorization. Does not sign, reserve the name, create, pay, o
create_grynvault_nip05_invoice — After separate explicit user confirmation, sign the prepared authorization and create exactly one pending 2,000-sat name@frontiercrown.com invoice. Does not pay

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.frontiercrown.signer/nostr-signer

first seen 28 d ago · fetched 19 h agoopen ↗

Field history (6 recent events)

28 d ago · declared · summary → "Approve Nostr signatures with your own browser signer without exposing a private key."
28 d ago · declared · description → "Approve Nostr signatures with your own browser signer without exposing a private key."
28 d ago · declared · publisherName → "com.frontiercrown.signer"
28 d ago · declared · repoUrl → "https://github.com/hudhaifahz/nostr-signer-chatgpt"
28 d ago · declared · version → "0.4.0"
28 d ago · declared · protocols → ["mcp"]

Nostr Signer

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from