A
licenseNot graded
qualityC
maintenanceEnables LLM coding agents to sign in with Nostr by generating NIP-07 signatures and exposing public keys, without requiring a wallet or browser extension.
13 npm
MIT
Nostr Signer
Server Details
Approve Nostr signatures with your own browser signer without exposing a private key.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- hudhaifahz/nostr-signer-chatgpt
- GitHub Stars
- 0
- Server Listing
- Nostr Signer
- ChatGPT
- –
- Claude
- –
TDQS
A3.7/5.0
Scored across 17 tools
Disambiguation4/5
Most tools have clearly distinct purposes, and the prepare/create invoice pairs form a legible two-step flow. The main overlap is prepare_event vs prepare_note (a kind:1 note is itself an event), and connect_bunker vs begin_nostrconnect_pairing both describe pairing methods, though descriptions do differentiate them.
Naming Consistency5/5
Every tool uses a consistent snake_case verb_noun pattern (approve_, begin_, connect_, create_, disconnect_, get_, prepare_, publish_, query_, sign_). Verbs are unambiguous action prefixes applied uniformly across all clusters.
Tool Count4/5
17 tools is slightly on the heavy side but justified by three coherent sub-domains: signer connection, Nostr event lifecycle, and Grynvault billing. Each tool appears to earn its place rather than being redundant filler.
Completeness4/5
The surface covers the full local lifecycle: connection management (setup, connect, status, pubkey, disconnect), event prep/sign/publish/query, and Grynvault invoice preparation and dashboard. Minor gaps exist (e.g. event deletion or profile kind:0 publishing), but core workflows are fully supported.
Available Tools
17 toolsapprove_grynvault_browser_handoffApprove Grynvault in-app browser sign-inAInspect
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, publish a Nostr event, change settlement, or grant wallet custody.
Inputs: code (required), confirm_browser_sign_in (required).
begin_nostrconnect_pairingBegin signer pairingBInspect
Advanced fallback: create a nostrconnect:// URI for the user to scan or open in a remote signer. Never accepts an nsec.
Inputs: relays.
connect_bunkerConnect bunker signerAInspect
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 nsec.
Inputs: connection_uri (required).
create_grynvault_nip05_invoiceCreate Frontier Crown NIP-05 invoiceAInspect
After separate explicit user confirmation, sign the prepared authorization and create exactly one pending 2,000-sat name@frontiercrown.com invoice. Does not pay, settle, activate, or prove identity.
Inputs: operation_id (required), confirm_invoice_creation (required).
create_grynvault_supporter_invoiceCreate Grynvault supporter invoiceAInspect
After separate explicit user confirmation, sign the prepared authorization and create exactly one pending Grynvault supporter invoice. Does not pay it and never treats a redirect as settlement.
Inputs: operation_id (required), confirm_invoice_creation (required).
disconnect_signerDisconnect signerADestructiveInspect
Forget the in-memory signer session and all prepared events.
Inputs: confirm_disconnect (required).
get_grynvault_account_dashboardGet signed Grynvault account dashboardARead-onlyInspect
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 or change settlement.
Inputs: confirm_account_access (required).
get_public_keyGet public keyBRead-onlyInspect
Return the public key exposed by the currently paired signer.
Inputs: no named parameters.
get_setup_urlGet signer setup URLARead-onlyInspect
Return the loopback-only page used to connect a NIP-07 browser extension or an advanced NIP-46 signer.
Inputs: no named parameters.
get_signer_statusGet signer statusARead-onlyInspect
Check whether a user-controlled NIP-07 or NIP-46 signer is connected.
Inputs: no named parameters.
prepare_eventPrepare exact Nostr eventARead-onlyInspect
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.
Inputs: event (required).
prepare_grynvault_nip05_invoicePrepare Frontier Crown NIP-05 invoiceARead-onlyInspect
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, or settle an invoice.
Inputs: name (required).
prepare_grynvault_supporter_invoicePrepare Grynvault supporter invoiceARead-onlyInspect
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 sign, create, pay, or settle an invoice.
Inputs: plan (required), donation_sats.
prepare_notePrepare Nostr noteARead-onlyInspect
Prepare and bind an exact unsigned kind:1 note for user review. This does not sign or publish.
Inputs: content (required).
publish_eventPublish signed eventBDestructiveInspect
Publish a previously verified signed event to configured relays. Requires separate explicit user intent.
Inputs: intent_id (required), confirm_publish (required), relays.
query_eventsRead Nostr eventsBRead-onlyInspect
Read a bounded set of verified public profile or note events from selected relays.
Inputs: kinds, limit, since, relays, +1 more.
sign_eventRequest event signatureAInspect
Ask the paired signer to approve and sign the exact event bound to a fresh intent. Requires explicit user intent and never publishes.
Inputs: intent_id (required), confirm_signature (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Explains wallet approvals and signature requests in plain language: SAFE, CAUTION or RISK.
Read-only crypto safety: token honeypot checks, EIP-712 signature decode, approval scans.
Let AI agents use any website you're logged in to. Sessions stay encrypted on your machine.
Connect AI agents to your own Chrome with scoped access, approvals, and verified task results.
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables AI agents to authorize API requests, verify and sign stamped on-chain actions, and send transactions across supported EVM chains while keeping private keys on the local machine.6580 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables remote MCP servers to request wallet approvals, signatures, and transactions through an approval URL while keeping private keys in the user's browser wallet.27 npmMIT
- AlicenseAqualityDmaintenanceLocal MCP-to-browser signing bridge for EVM, Solana, and Sui, letting agents prepare and simulate transactions while users approve and sign in a browser wallet extension.6MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.