Access control for AI agents and MCP servers: allow, hold for approval, or block each tool call
Nostr Signer is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Approve Nostr signatures with your own browser signer without exposing a private key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http nostr-signer-mcp https://signer.frontiercrown.com/mcp
# 2 — ask your agent for something these tools do
# get_setup_url, get_signer_status, begin_nostrconnect_pairing and 14 more
Nostr Signer costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http nostr-signer-mcp https://signer.frontiercrown.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Return the loopback-only page used to connect a NIP-07 browser extension or an advanced NIP-46 signer.
No parameter schema on file.
Check whether a user-controlled NIP-07 or NIP-46 signer is connected.
No parameter schema on file.
Advanced fallback: create a nostrconnect:// URI for the user to scan or open in a remote signer. Never accepts an nsec.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| relays | array | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| connection_uri | string | yes | — |
Return the public key exposed by the currently paired signer.
No parameter schema on file.
Prepare and bind an exact unsigned kind:1 note for user review. This does not sign or publish.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| content | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event | object | yes | — |
Ask the paired signer to approve and sign the exact event bound to a fresh intent. Requires explicit user intent and never publishes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| intent_id | string | yes | — |
| confirm_signature | boolean | yes | Must be true only after the user explicitly approved this action. |
Publish a previously verified signed event to configured relays. Requires separate explicit user intent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| intent_id | string | yes | — |
| confirm_publish | boolean | yes | Must be true only after the user explicitly approved this action. |
| relays | array | no | — |
Read a bounded set of verified public profile or note events from selected relays.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| relays | array | no | — |
| authors | array | no | — |
| kinds | array | no | — |
| limit | integer | no | — |
| since | integer | no | — |
Forget the in-memory signer session and all prepared events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| confirm_disconnect | boolean | yes | Must be true only after the user explicitly approved this action. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| confirm_account_access | boolean | yes | Must be true only after the user approved signing a read-only Grynvault account request. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The one-time code displayed by the Grynvault portal, for example ABCD-EFGH-JKLM. |
| confirm_browser_sign_in | boolean | yes | Must be true only after the user asked to sign the displayed Grynvault browser code. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan | string | yes | — |
| donation_sats | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation_id | string | yes | — |
| confirm_invoice_creation | boolean | yes | Must be true only after the user explicitly approved this action. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation_id | string | yes | — |
| confirm_invoice_creation | boolean | yes | Must be true only after the user explicitly approved this action. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Nostr Signer or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.4.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Nostr Signer can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.