Skip to content

Nostr Signer MCP server

com.frontiercrown.signer/nostr-signersigner.frontiercrown.comstreamable-httpv0.4.0Scanned

Approve Nostr signatures with your own browser signer without exposing a private key.

17 tools: 2 can delete or cancel things, 9 change things and 6 only read.

Tools: 2 delete, 0 irreversible, 9 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 12
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Nostr Signer MCP server can do

The Nostr Signer MCP server is published by signer.frontiercrown.com, a domain the MCP Registry verified. It has 17 tools. It can delete or cancel things (2 tools: publish_event and disconnect_signer) and create or change data (9 tools: begin_nostrconnect_pairing, connect_bunker, prepare_note, sign_event and 5 more). 6 tools only read.

1 tool reads private data (query_events); 12 tools bring in text other people can write (get_setup_url, begin_nostrconnect_pairing, connect_bunker and 9 more); 1 tool can send data out of your system (publish_event). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 0.4.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

17 tools

Deletes or cancels 2Claude Code: deny
  • disconnect_signerForget the in-memory signer session and all prepared events.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Forget the in-memory signer session and all prepared events.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • publish_eventPublish a previously verified signed event to configured relays.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "publish_event" says "publish": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "publish_event" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Publish a previously verified signed event to configured relays. Requires separate explicit user intent.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
Changes things 9Claude Code: ask
  • approve_grynvault_browser_handoffSign a short-lived, read-only Grynvault account handoff code so the browser tab that created it can receive its own dashboard.Reads text others writeNo findings

    Why it is in this group

    • The name "approve_grynvault_browser_handoff" says "approve": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • begin_nostrconnect_pairingAdvanced fallback: create a nostrconnect:// URI for the user to scan or open in a remote signer.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Advanced fallback: create a nostrconnect:// URI for the user to scan or open in a remote signer. Never accepts an nsec.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • connect_bunkerConnect a bunker:// URI only when the user knowingly supplied it.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • create_grynvault_nip05_invoiceAfter separate explicit user confirmation, sign the prepared authorization and create exactly one pending 2,000-sat name@frontiercrown.com invoice.Reads text others writeNo findings

    Why it is in this group

    • The name "create_grynvault_nip05_invoice" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • create_grynvault_supporter_invoiceAfter separate explicit user confirmation, sign the prepared authorization and create exactly one pending Grynvault supporter invoice.Reads text others writeNo findings

    Why it is in this group

    • The name "create_grynvault_supporter_invoice" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • prepare_grynvault_nip05_invoiceCheck and normalize a name@frontiercrown.com identifier, then prepare its exact 2,000-sat invoice authorization.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • prepare_grynvault_supporter_invoicePrepare 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • prepare_notePrepare and bind an exact unsigned kind:1 note for user review.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Prepare and bind an exact unsigned kind:1 note for user review. This does not sign or publish.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • sign_eventAsk the paired signer to approve and sign the exact event bound to a fresh intent.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Ask the paired signer to approve and sign the exact event bound to a fresh intent. Requires explicit user intent and never publishes.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
Only reads 6Show 6 read-only tools
  • get_grynvault_account_dashboardRead the connected Nostr identity's Grynvault supporter, payment, and NIP-05 dashboard using a short-lived signed authorization.Reads text others writeNo findings

    Why it is in this group

    • The name "get_grynvault_account_dashboard" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_public_keyReturn the public key exposed by the currently paired signer.No findings

    Why it is in this group

    • The name "get_public_key" says "get": a word for reading.
    Description, as the server wrote it
    Return the public key exposed by the currently paired signer.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_setup_urlReturn the loopback-only page used to connect a NIP-07 browser extension or an advanced NIP-46 signer.Reads text others writeNo findings

    Why it is in this group

    • The name "get_setup_url" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_setup_url" says "get" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "return" and "browser": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Return the loopback-only page used to connect a NIP-07 browser extension or an advanced NIP-46 signer.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_signer_statusCheck whether a user-controlled NIP-07 or NIP-46 signer is connected.No findings

    Why it is in this group

    • The name "get_signer_status" says "get": a word for reading.
    Description, as the server wrote it
    Check whether a user-controlled NIP-07 or NIP-46 signer is connected.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • prepare_eventValidate and bind an exact unsigned Nostr event for user review.No findings

    Why it is in this group

    • The description's first verb is "validate": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • query_eventsRead a bounded set of verified public profile or note events from selected relays.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "query_events" says "query": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "note": it reads notes.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Read a bounded set of verified public profile or note events from selected relays.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

12 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__nostr-signer__publish_event"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:38 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
11
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 11 tools that change things (2 destructive, 9 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://signer.frontiercrown.com/mcp: tools/list returned 17 tools to an anonymous client, including publish_event (destructive), disconnect_signer (destructive), begin_nostrconnect_pairing (write), connect_bunker (write), prepare_note (write) and 6 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.4.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http nostr-signer https://signer.frontiercrown.com/mcp
claude mcp add --transport http nostr-signer https://signer.frontiercrown.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__nostr-signer__get_setup_url",
      "mcp__nostr-signer__get_signer_status",
      "mcp__nostr-signer__get_public_key",
      "mcp__nostr-signer__prepare_event",
      "mcp__nostr-signer__query_events",
      "mcp__nostr-signer__get_grynvault_account_dashboard"
    ],
    "ask": [
      "mcp__nostr-signer__begin_nostrconnect_pairing",
      "mcp__nostr-signer__connect_bunker",
      "mcp__nostr-signer__prepare_note",
      "mcp__nostr-signer__sign_event",
      "mcp__nostr-signer__approve_grynvault_browser_handoff",
      "mcp__nostr-signer__prepare_grynvault_supporter_invoice",
      "mcp__nostr-signer__create_grynvault_supporter_invoice",
      "mcp__nostr-signer__prepare_grynvault_nip05_invoice",
      "mcp__nostr-signer__create_grynvault_nip05_invoice"
    ],
    "deny": [
      "mcp__nostr-signer__publish_event",
      "mcp__nostr-signer__disconnect_signer"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nostr-signer. Review it before you use it.

Capability tags behind 12 rules
  • mcp__nostr-signer__get_setup_url untrusted-input
  • mcp__nostr-signer__begin_nostrconnect_pairing untrusted-input
  • mcp__nostr-signer__connect_bunker untrusted-input
  • mcp__nostr-signer__sign_event untrusted-input
  • mcp__nostr-signer__publish_event untrusted-input, outbound
  • mcp__nostr-signer__query_events private-data, untrusted-input
  • mcp__nostr-signer__get_grynvault_account_dashboard untrusted-input
  • mcp__nostr-signer__approve_grynvault_browser_handoff untrusted-input
  • mcp__nostr-signer__prepare_grynvault_supporter_invoice untrusted-input
  • mcp__nostr-signer__create_grynvault_supporter_invoice untrusted-input
  • mcp__nostr-signer__prepare_grynvault_nip05_invoice untrusted-input
  • mcp__nostr-signer__create_grynvault_nip05_invoice untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.frontiercrown.signer/nostr-signer/verify?hash=98900261cc5073ff2cce3cdfca0d24a26e41fb1bd3dfd6d251c3325277ceb71b" | jq -e '.changed == false'

Pinned hash 98900261cc50, from Nov 10, 2026, 16:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.frontiercrown.signer/nostr-signer/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.frontiercrown.signer/nostr-signer
[![Anlyon Radar](https://radar.anlyon.com/badge/com.frontiercrown.signer/nostr-signer.svg)](https://radar.anlyon.com/servers/com.frontiercrown.signer/nostr-signer)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:55 UTC.

Nostr Signer MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Nostr Signer MCP server safe?

No scan can promise that. What its definitions show: 17 tools, 11 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Nostr Signer MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: publish_event and disconnect_signer.

Can the Nostr Signer MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Nostr Signer MCP server have?

17 tools: 2 destructive, 9 write, 6 read. publish_event, disconnect_signer, begin_nostrconnect_pairing, connect_bunker, prepare_note, sign_event, approve_grynvault_browser_handoff, prepare_grynvault_supporter_invoice and 9 more.

Does the Nostr Signer MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Nostr Signer MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): publish_event.

Has the Nostr Signer MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.