Nostr Signer is answering right now. Last checked 7 min ago. It exposes 17 tools. Last commit 11 Sep 2026.
Approve Nostr signatures with your own browser signer without exposing a private key.
Uptime history
53 days of history · worst day 98%
53 days agonow
100.0%
Uptime 24h
91 of 91 checks
17
Tools
read from the server
401 ms
Response time
average over 24h
0
Stars
last commit 11 Sep 2026
Nothing serious here today
Today is the operative word: we check Nostr Signer every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.
run in your terminal
claude mcp add nostr-signer --transport http https://signer.frontiercrown.com/mcpSettings → Connectors → Add custom connector, then paste this address
https://signer.frontiercrown.com/mcp~/.codex/config.toml
[mcp_servers.nostr-signer]
url = "https://signer.frontiercrown.com/mcp".cursor/mcp.json
{
"mcpServers": {
"nostr-signer": {
"url": "https://signer.frontiercrown.com/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"nostr-signer": {
"type": "http",
"url": "https://signer.frontiercrown.com/mcp"
}
}
}Available tools 17
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
prepare
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.
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 name, create, pay, or settle 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 sign, create, pay, or settle an invoice.
prepare_note
Prepare and bind an exact unsigned kind:1 note for user review. This does not sign or publish.
grynvault
create_grynvault_nip05_invoice
After separate explicit user confirmation, sign the prepared authorization and create exactly one pending 2,000-sat [email protected] invoice. Does not pay, settle, activate, or prove identity.
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 treats a redirect as settlement.
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 or change settlement.
approve
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, publish a Nostr event, change settlement, or grant wallet custody.
begin
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
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 nsec.
disconnect
disconnect_signer
Forget the in-memory signer session and all prepared events.
events
query_events
Read a bounded set of verified public profile or note events from selected relays.
public
get_public_key
Return the public key exposed by the currently paired signer.
publish
publish_event
Publish a previously verified signed event to configured relays. Requires separate explicit user intent.
setup
get_setup_url
Return the loopback-only page used to connect a NIP-07 browser extension or an advanced NIP-46 signer.
sign
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.
signer
get_signer_status
Check whether a user-controlled NIP-07 or NIP-46 signer is connected.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://signer.frontiercrown.com/mcp | streamable-http | answering | 512 ms | 7 min ago |
Alternatives to Nostr Signer
same job, measured the same wayUISandbox
by ideelab
Play with your app's design in the browser: load a build, turn the knobs, export the code.
Node Command
by huseyincig
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
opointo
by opointo
Design a React Native app in a browser and emit it as a real Expo project you own, iOS and Android.
C
Conecto E-signature
by conecto
PDFs signed in the browser and sealed with a signing certificate. Pay per action.
NextCore Browser
by homestaynextcore
Multi-profile browser: AI agents create, open and drive isolated signed-in profiles with own proxy
Maxoperf
by maxoperf
Load & browser performance testing — drive MaxoPerf from your AI agent with your API key.
Sitekick CMS
by aketchel
Plan and improve WordPress websites with generation, previews, and browser-approved publishing.
UXMachine
by qtorb
Website checker for AI coding agents. Measures your site in a real browser, with evidence.
Nostr Signer — questions
Answers built from our own checks of this server.
What can Nostr Signer do?
It exposes 17 tools, read directly from the server on our last check. Among them: approve_grynvault_browser_handoff, begin_nostrconnect_pairing, connect_bunker, create_grynvault_nip05_invoice, create_grynvault_supporter_invoice, disconnect_signer and 11 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Nostr Signer mostly used for?
Its tools cluster around prepare and grynvault. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Nostr Signer working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 401 ms. The bar chart above shows every period we have measured.
How do I connect Nostr Signer?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Nostr Signer need an API key?
No. Nostr Signer completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 17 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Nostr Signer?
It answers our handshake in 401 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Nostr Signer open source?
The code is open source: it is published under the Apache-2.0 licence, written in JavaScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at signer.frontiercrown.com, which runs on its operator's own terms.