Nostr Signer
Approve Nostr signatures with your own browser signer without exposing a private key.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http nostr-signer 'https://signer.frontiercrown.com/mcp'
{
"mcpServers": {
"nostr-signer": {
"type": "http",
"url": "https://signer.frontiercrown.com/mcp"
}
}
}
Frequently asked questions
What is Nostr Signer?
Approve Nostr signatures with your own browser signer without exposing a private key.
How do I install Nostr Signer?
It runs as a remote server. In Claude Code: claude mcp add --transport http nostr-signer 'https://signer.frontiercrown.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Nostr Signer need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Nostr Signer open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains Nostr Signer?
It is published by hudhaifahz. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.