Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Nostr Signer

✓ signer.frontiercrown.com

by hudhaifahzversion 0.4.0i★ 0iRuns in the cloudOfficial site ↗
Registry namecom.frontiercrown.signer/nostr-signer

How to install

What it does

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

  • Connects Runs in the cloud
  • Account or key No key needed
  • Category Web & browsers

Use together with

Skills that teach the AI this kind of work; they work alongside this one

timesfm

TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.

by google-research★ 35,6381 skills

Skill · How-to guide

Shadowbroker

Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…

by BigBodyCobain★ 11,6051 skills

Skill · How-to guide

google-maps-scraper

scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place

by gosom★ 8,2361 skills

Skill · How-to guide

Why it ranks here

This one is in the “Apps that connect to AI” tab, which is ordered without stars, in this order

1. In Claude’s connector directoryNo
2. Tried by our teamNo
3. Works for Thai usersNo
4. Usage without stars15/100Popularity 0 · Freshness 7 · Still answering 8 · Likes from users +0
5. Listed on2026-09-11

Likes from users: 0 · Adds at most 5 points to the order (1 per person). It cannot be bought.

Quality: Passed 4/4 basic checks (shown, not used for ordering)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Nostr Signer. Follow https://mcp.popnx.com/i/frontiercrown-signer-nostr-signer.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 4/4 checks · What you ask goes through the maker’s server (signer.frontiercrown.com) · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude · about 2 min

No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it

  1. Open Claude’s Connectors page

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. Click “Add” → “Custom” → “Web” and fill in these 2 fields

    Copy each value into the field with the same name in Claude, then click Continue

    Name · NameNostr Signer
    Remote MCP server URL · Addresshttps://signer.frontiercrown.com/mcp

    Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add

  3. Turn it on in a chat

    +ConnectorsNostr Signer

  4. Try it

    Use Nostr Signer and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Nostr Signer or shows a Nostr Signer tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with ChatGPT, depending on your plan

Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only

  1. Open ChatGPT’s add-MCP page on the web

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. Fill in the name and address

    Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin

    Name · NameNostr Signer
    Connection · Addresshttps://signer.frontiercrown.com/mcp
  3. Pick Nostr Signer in a chat

    Start a new chat and pick Nostr Signer from your plugins before typing

  4. Try it

    Use Nostr Signer and tell me what you can do for me, then show me one thing

    ✓ If ChatGPT says it is using Nostr Signer or shows a Nostr Signer tool in the answer, you are connected

Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Claude Code · about 2 min

No key, nothing to install

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  2. Paste this command and press Enter

    claude mcp add --transport http --scope user nostr-signer https://signer.frontiercrown.com/mcp
  3. Type /mcp in Claude Code

    You should see Nostr Signer listed as connected

  4. Try it

    Use Nostr Signer and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Nostr Signer or shows a Nostr Signer tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor · about 2 min

No key, nothing to install

  1. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  2. Open the AI chat in Cursor in Agent mode

  3. Try it

    Use Nostr Signer and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Nostr Signer or shows a Nostr Signer tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code · about 2 min

No key, nothing to install

  1. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  2. Open the AI chat in VS Code in Agent mode

  3. Try it

    Use Nostr Signer and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Nostr Signer or shows a Nostr Signer tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

Address for apps that connect over the web

Addresshttps://signer.frontiercrown.com/mcp

JSON settings are under “For developers” below

Stuck? Ask people who use Nostr Signer💬 Discussion →
For developers: Terminal commands and JSON settings

Over the web

Claude Code

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

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "nostr-signer": {
      "url": "https://signer.frontiercrown.com/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "nostr-signer": {
      "type": "http",
      "url": "https://signer.frontiercrown.com/mcp"
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
Not on npm/PyPI
Verified domain
✓ signer.frontiercrown.com
Licencei
Apache-2.0
Connection
Runs in the cloud
Transport
streamable-http
Latest versioni
0.4.0
Published to registryi
Sep 11, 2026
Code last changedi
Sep 11, 2026
Last checked
Nov 14, 2026
Maker
hudhaifahz
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

All apps, with pros and cons →

Related guides

What it can do

Tool names and descriptions exactly as the server reported them on Nov 14, 2026. The maker wrote them, not us; we show them as plain text.

  • get_setup_url

    Return the loopback-only page used to connect a NIP-07 browser extension or an advanced NIP-46 signer.

  • get_signer_status

    Check whether a user-controlled NIP-07 or NIP-46 signer is connected.

  • 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_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.

  • get_public_key

    Return the public key exposed by the currently paired signer.

  • prepare_note

    Prepare and bind an exact unsigned kind:1 note for user review. This does not sign or publish.

  • 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.

  • 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.

  • publish_event

    Publish a previously verified signed event to configured relays. Requires separate explicit user intent.

  • query_events

    Read a bounded set of verified public profile or note events from selected relays.

  • disconnect_signer

    Forget the in-memory signer session and all prepared events.

  • 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_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.

  • 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.

  • 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.

  • prepare_grynvault_nip05_invoice

    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.

  • create_grynvault_nip05_invoice

    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.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain signer.frontiercrown.com (the registry checks domain ownership)

  • ✓ Pass

    Still maintained

    Code last changed 2 months ago

  • – Not applicable

    Has a licence

    Not applicable: a cloud server run by the owner of signer.frontiercrown.com; you don't run code from the repo

  • ✓ Pass

    Endpoint responds

    Responded in 239 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 17 tool descriptions and found no hidden instructions to the AI

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/frontiercrown-signer-nostr-signer.svg)](https://mcp.popnx.com/en/servers/frontiercrown-signer-nostr-signer)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Web & browsersi

  • More stars than 0% of the other 1645 servers in this category
  • Published to the registry more recently than 26% of the other 1645 servers in this category
  • Basic checks equal to or better than 99% of the other 1645 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Nostr Signer safe?

It passed 4 of 4 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed 2 months ago, and the latest version (0.4.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).

What can I use instead?

In the same category: Browser Use, changedetection.io (official), Apify MCP Server, Pomerado, Actionbook

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.

by browser-useWidely used↓ 1.7M/wk★ 121.5KUpdated 30 days ago

Computer or cloud✓ service owner · browser-use.com

Apify MCP Server

Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡

by apifyWidely used★ 17KUpdated 3 days ago

Runs in the cloud✓ service owner · apify.com

Pomerado

Connect your agents to any website. The cheaper, faster and more reliable alternative to browser use

by PomeradoGrowing★ 1.8KUpdated 2 days ago

Runs in the cloud✓ service owner · pomerado.ai

Actionbook

Let your AI agent operate any website through a real, logged-in browser session.

by actionbookGrowing★ 1.6KUpdated 32 days ago

Runs in the cloud✓ service owner · actionbook.app
Compared with similar ones
This one
Nostr Signer
Browser Usechangedetection.io (official)Apify MCP ServerPomeradoActionbook
Runs whereRuns in the cloud, nothing to installCloud or install on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoYesNoYesNoNo
Add with + in ClaudeNoYesNoNoNoNo
Basic checks4/45/53/34/44/44/4
LicenseApache-2.0MITApache-2.0MITMITApache-2.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Nostr Signer for ChatGPT and Codex

A local-first, open-source signer bridge that lets ChatGPT Work or Codex request Nostr signatures from Alby, nos2x, another NIP-07 browser extension, or an advanced NIP-46 remote signer. The signer keeps the private key. This project never needs, accepts, stores, logs, or transmits an nsec.

Use the local installation for the strongest security. It keeps the approval page and session

coordinator on your computer. The hosted bridge is a convenience beta: event contents, public keys,

signatures, ciphertext, and relay responses transit infrastructure operated by Frontier Crown on

Railway. Hosted NIP-44 encryption and decryption are disabled because plaintext could otherwise

transit that infrastructure.

Release status: v0.4.0 local public beta plus a live accountless hosted alpha. Live Chrome-family NIP-07 public-key access and signing succeeded on 2026-09-10. A user-approved announcement was accepted and independently read back with a valid signature from nos.lol, nostr.mom, and relay.primal.net. The hosted MCP endpoint at https://signer.frontiercrown.com/mcp completed external initialization and two-session pairing-page isolation tests. Its reduced hosted surface exposes 17 tools and omits NIP-44 encrypt/decrypt. It is active in the official MCP Registry but has not been approved by the OpenAI directory.

Will it work for everyone?

Not universally. The current release is for desktop users who can run Node.js 22+, connect a local stdio MCP server, and open the approval page in a Chrome- or Firefox-family profile with a compatible NIP-07 extension. It is not a mobile signer or unattended signing daemon. Prefer a signer that displays the complete event—including kind, content, tags, and timestamp—before every approval.

The free local plugin is the primary, recommended public release because each user keeps the key and runs the bridge. It needs no OAuth or separate account: the browser extension supplies the Nostr public key and approves each signature. The hosted prototype also has no OAuth or user accounts: it binds each AI MCP session to an extension-enabled browser with a short-lived, high-entropy capability URL. It still needs per-session isolation, abuse controls, privacy/retention operations, and an independent security review. See LAUNCH_READINESS.md, COMPATIBILITY.md, and HOSTED_SERVICE.md.

Install in Codex

Clone the public source, verify the release tag, build it locally, and register the bundled MCP server. Then start a new Codex task so its tools are loaded:

git clone --branch v0.4.0 https://github.com/hudhaifahz/nostr-signer-chatgpt.git

cd nostr-signer-chatgpt npm ci npm run check codex mcp add nostr-signer -- node "$PWD/mcp/server.mjs"

The repository includes portable plugin manifests, but a one-command Grynvault marketplace wrapper is not published yet. Inspect the source and release tag before installing; the local signer bridge runs with the permissions of the desktop user who starts it.

Download the prebuilt local bundle

The release page includes a prebuilt archive and SHA-256 checksum. It contains the standalone MCP bundle, plugin manifests, signer skill, license notices, source, tests, and documentation. It does not contain a private key, signer session, or browser data.

Build hashes and the live deployment's claimed source revision are documented in PROVENANCE.md and published at https://signer.frontiercrown.com/provenance. Tagged archives receive GitHub build provenance attestations.

curl -LO https://github.com/hudhaifahz/nostr-signer-chatgpt/releases/download/v0.4.0/nostr-signer-chatgpt-0.4.0.tgz

curl -LO https://github.com/hudhaifahz/nostr-signer-chatgpt/releases/download/v0.4.0/nostr-signer-chatgpt-0.4.0.tgz.sha256 shasum -a 256 -c nostr-signer-chatgpt-0.4.0.tgz.sha256 mkdir nostr-signer-chatgpt tar -xzf nostr-signer-chatgpt-0.4.0.tgz -C nostr-signer-chatgpt --strip-components=1 codex mcp add nostr-signer -- node "$PWD/nostr-signer-chatgpt/mcp/server.mjs"

Expected SHA-256 for the v0.4.0 bundle: 75d2c2cc7070ce0a15dbc122c479c312919279ff4160ed9e7e1993c335ce95a5.

The ordinary-user journey

  1. Install and start the plugin locally.
  2. Open the local setup page at http://127.0.0.1:34846/ in the Chrome or Firefox profile where Alby, nos2x, or another NIP-07 signer is installed.
  3. Click Connect browser extension once and approve public-key access in the extension. Keep this page open.
  4. Ask ChatGPT or Codex to prepare a Nostr note.
  5. Review the exact note. Tell ChatGPT or Codex to request the signature.
  6. The local page shows the exact pending operation. Click Continue in extension, then approve in the extension if it asks.
  7. Separately tell ChatGPT or Codex to publish. A post is reported live only when at least one relay acknowledges it.

To use the same signer inside a NIP-46-capable app such as Noornote or YakiHonne, connect the browser extension first, click Create app sign-in link, copy the private bunker:// link, and paste it into the app's Remote signer or Bunker login. Return to the local page to approve the exact client public key and every subsequent signing, encryption, or decryption request. The link expires, is valid for one approved client, and must be treated like a temporary password.

For Grynvault in the Codex in-app browser, open https://frontiercrown.com/portal, click Sign in with Codex signer, and ask Codex to approve the exact short code using this plugin. The portal tab keeps a separate high-entropy secret; the short code only locates the pending request. The signed authorization returns that public key's read-only account dashboard to the originating tab and does not publish an event, create an invoice, change settlement, or grant wallet custody.

Never paste an nsec, raw private key, seed phrase, or backup into ChatGPT, Codex, the setup page, or a tool call. If an nsec was exposed, rotate it in a trusted signer outside this project.

Architecture

flowchart LR

U[User] --> C[ChatGPT Work or Codex] U --> E[Alby, nos2x, or NIP-07 extension] U --> S[Advanced NIP-46 signer] U --> A[Noornote, YakiHonne, or another NIP-46 app] C -->|focused MCP tools| P[Local plugin process] B[Local approval page\n127.0.0.1 only] <--> P B -->|window.nostr request| E E -->|signed or encrypted result| B P -->|NIP-46 encrypted requests| R[(Configured Nostr relays)] A -->|NIP-46 encrypted requests| R R -->|approval-gated responses| P R -->|NIP-46 events| S S -->|approve or reject| R P -->|verified signed event\nafter separate publish intent| R

K[nsec] -. remains inside signer .-> E K -. remains inside signer .-> S

The code separates the signer interface, session/intent state, relay gateway, MCP adapter, and local UI. A future MCP Apps component, WebMCP site tool, hardware signer, or different transport can reuse the service layer without changing event-validation policy.

What is implemented

  • Primary NIP-07 bridge for Alby, nos2x, and compatible extensions: one local connection, one queued approval at a time, random request IDs, stale-response rejection, and no private-key access.
  • Advanced bunker:// and client-generated nostrconnect:// flows using nostr-tools NIP-46 support.
  • Experimental remote-signer mode for third-party NIP-46 clients. It creates a one-client, short-lived bunker:// link, accepts both NIP-44 and legacy NIP-04 encrypted RPC transport, and requires local approval for connect, event signing, NIP-04, and NIP-44 operations.
  • get_public_key, exact generic-event and kind:1 preparation, bound sign_event, nip44_encrypt, nip44_decrypt, separately confirmed publish_event, and bounded relay reads for kinds 0 and 1.
  • Exact unsigned-event validation, signature/hash verification, signer-pubkey binding, one-use signing intents, timeouts, session expiry, and stale-pairing rejection.
  • Per-relay publication acknowledgements. No success claim when every relay rejects or times out.
  • In-memory-only signer sessions. Restarting or disconnecting forgets pairing material and prepared events.
  • A localhost-only setup page with a per-process anti-CSRF token, request size limit, no external scripts, and no persistence.
  • Redacted structured logs and hard rejection of nsec-like input.
  • Signed Grynvault account-dashboard access plus separately prepared/confirmed supporter and 2,000-sat name@frontiercrown.com NIP-05 invoice requests. An invoice response is always reported as pending, never as payment or settlement.
  • Short-lived Grynvault in-app browser handoff approval bound to the exact HTTPS URL, challenge, code, and payload hash. Only the browser holding the separate secret can claim its read-only dashboard.
  • Portable Agent Plugins manifests plus the scaffolded Codex compatibility manifest.
  • A deterministic safe simulated signer/relay path for CI and onboarding.

Local setup

Requirements: Node.js 22 or later and npm. Use a test Nostr identity for the public beta.

npm ci

cp .env.example .env npm run build npm start

Set NOSTR_RELAYS to comma-separated wss:// relay URLs before live pairing or publication. The example file contains starting values, not an availability guarantee. ws:// is rejected except for localhost/loopback test relays.

The setup page binds to and accepts only 127.0.0.1. Open it in the browser profile containing your NIP-07 extension—not the Codex in-app browser unless that browser actually has such an extension. Connect once and keep the tab open while signing. The page queues the exact request and requires a browser-side click before calling window.nostr. That interaction gate is not proof of human presence when the host also has browser automation, so the extension's own approval policy remains the final protection.

The advanced section accepts a bunker: URI only in memory and never logs it. A generated nostrconnect: URI contains an ephemeral pairing secret; treat it as sensitive and do not post it publicly.

The experimental third-party-app section makes this plugin act as the remote signer. Its generated bunker:// link is shown only on the loopback page and is not exposed as an MCP tool. One client can be connected at a time. Stopping the bridge, restarting the process, or reaching the session expiry invalidates that app connection; reconnect the app with a new link.

Local demo

The safe onboarding demo exercises prepare → sign → verify → publish entirely in memory:

npm run demo

The output includes a simulated public key, event ID, and relay acknowledgement. It does not prove compatibility with a live signer or public relay.

To inspect the real MCP tool surface locally:

npm run build

npx @modelcontextprotocol/inspector node mcp/server.mjs

To connect this checkout directly to a local Codex host without installing a marketplace package:

codex mcp add nostr-signer -- node /absolute/path/to/nostr-signer-chatgpt/mcp/server.mjs

Then restart the ChatGPT desktop app/Codex host and use /mcp or MCP settings to verify the server. For a packaged install, use the included plugin.json, mcp.json, .codex-plugin/plugin.json, .mcp.json, skill, and committed mcp/server.mjs bundle in a local marketplace. The current OpenAI documentation distinguishes local Codex stdio support from ChatGPT web. The accountless hosted alpha is available at https://signer.frontiercrown.com/mcp; it uses short-lived capability sessions rather than OAuth.

OpenClaw currently documents support for Agent Plugin/Codex bundles. After downloading and unpacking the release, install the local directory (or the release archive, if your OpenClaw version accepts it), inspect the plugin, and restart OpenClaw:

openclaw plugins install /absolute/path/to/nostr-signer-chatgpt

openclaw plugins inspect nostr-signer-chatgpt

This package has

Only the beginning is shown; read the rest in the repo