get_signer_status — Nostr Signer MCP Tool Read-only
get_signer_status
(get signer status) is one of 17 tools on the
Nostr Signer
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_signer_status from your client
- Claude Code Nostr Signer get_signer_status run in your project directory
- Claude Desktop Nostr Signer get_signer_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Nostr Signer get_signer_status ~/.cursor/mcp.json
- VS Code Nostr Signer get_signer_status .vscode/mcp.json
- Zed Nostr Signer get_signer_status ~/.config/zed/settings.json
- Windsurf Nostr Signer get_signer_status ~/.codeium/windsurf/mcp_config.json
- Cline Nostr Signer get_signer_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Nostr Signer get_signer_status ~/.gemini/settings.json
- Grok Nostr Signer get_signer_status .mcp.json (in your project root)
- ChatGPT Nostr Signer get_signer_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Nostr Signer get_signer_status Settings → Connectors → Add custom connector
- LangChain Nostr Signer get_signer_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nostr-signer https://signer.frontiercrown.com/mcpOther tools on this server
- get_setup_url
- begin_nostrconnect_pairing
- connect_bunker
- get_public_key
- prepare_note
- prepare_event
- sign_event
- publish_event
- query_events
- disconnect_signer
- get_grynvault_account_dashboard
- approve_grynvault_browser_handoff
- prepare_grynvault_supporter_invoice
- create_grynvault_supporter_invoice
- prepare_grynvault_nip05_invoice
- create_grynvault_nip05_invoice
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.