mcpField
N
nostr-ops-mcp

nostr-ops-mcp

Local
github.com/llmops-proSocial Media0Updated 19w ago

About nostr-ops-mcp

nostr-ops-mcp is an MCP server for AI agents that exposes NOSTR publishing, queries, identity encoding, and encrypted messaging. Write controls include kind and recipient allowlists, rate limits, optional confirmation, and an audit log.

Key features

  1. 01Publish and query NOSTR events
  2. 02Encode and decode NIP-19
  3. 03Verify NIP-05 identities
  4. 04Send and read encrypted DMs
  5. 05Write allowlists and rate limits
  6. 06Structured audit log

Use cases

  1. 01Publish scheduled NOSTR notes
  2. 02Query events and read profiles
  3. 03Monitor DMs and handle orders
  4. 04Constrain publishing under an identity

MCP support

The MCP server exposes NOSTR signing, publishing, querying, encoding, and DM tools to MCP clients. Writes can be controlled with allowlists, rate limits, optional confirmation, and audit logging.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"llmops-pro-nostr-ops": {
"command": "npx",
"args": [
"-y",
"nostr-ops-mcp"
],
"env": {
"NOSTR_RELAYS": "<NOSTR_RELAYS>",
"NOSTR_NIP46_URI": "<NOSTR_NIP46_URI>",
"NOSTR_PRIVATE_KEY": "<NOSTR_PRIVATE_KEY>",
"NOSTR_ALLOWED_KINDS": "<NOSTR_ALLOWED_KINDS>"
}
}
}
}
Run commandnpx -y nostr-ops-mcp
Environment variables to set
NOSTR_RELAYSComma-separated wss:// relay URLs
NOSTR_NIP46_URISecretNIP-46 bunker URI (preferred signer; keeps the nsec off this machine)
NOSTR_PRIVATE_KEYSecretnsec private key (alternative to NOSTR_NIP46_URI; read-only mode if neither is set)
NOSTR_ALLOWED_KINDSComma-separated event kinds the server may publish (required when a signer is configured)

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmnostr-ops-mcp0.2.3

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

nostr-ops-mcp

A NOSTR identity for your LLM agent. MCP server that exposes NOSTR protocol primitives — sign, publish, query, NIP-19 encode/decode, NIP-05 lookup, encrypted DMs — as tools your agent can call. Drop it into Claude Desktop, Claude Code, Cursor, or any MCP-speaking client. Hand the agent a NIP-46 bunker key (not a raw nsec). Set a kind allowlist. Let it post on your behalf within rails you control.

v0.1 — full read + write + DM surface. 16 tools wrapped in a defense-in-depth safety stack: kind allowlist (deny-by-default), recipient allowlist, rate limits, optional two-step confirmation, structured audit log. Supports both nsec (dev) and NIP-46 bunker (production).


What you can do with this

  • A bot that publishes kind:1 notes from your npub — daily summaries, scheduled posts, programmatic reactions to incoming events.
  • A NOSTR sales agent — pair with marketplace-mcp to publish NIP-15 stalls + products as the same identity.
  • Profile management — nostr_publish_metadata for kind:0 (always demands confirmation — overwriting your profile is irreversible without older relay data).
  • DM-driven workflows — a storefront agent that watches incoming DMs (with nostr_list_dms), decrypts orders, and replies via nostr_send_dm. Default-off behind NOSTR_DM_TOOLS_ENABLED.
  • Cross-server identity — share the same NIP-46 bunker URI across nostr-ops-mcp and marketplace-mcp. One key, one identity, two specialized tool surfaces.

The safety stack is the load-bearing reason this is usable in production: an agent with the keys to publish as you can ruin your reputation in seconds if unconstrained. The server enforces what kinds it'll sign, what rate, optional second-step confirmation, and writes every call to a structured audit log.


The sixteen tools

Read-only — local (no network, no signer needed)
ToolPurpose
nostr_decodeParse NIP-19 strings (npub / nsec / note / nevent / naddr / nprofile). nsec decoding gated behind NOSTR_ALLOW_NSEC_DECODE=true.
nostr_encodeBuild NIP-19 strings from raw fields. nsec encoding deliberately not supported.
Read-only — network (no signer needed for query/profile/nip05)
ToolPurpose
nostr_get_pubkeyReturns the signer's pubkey + npub. Errors clearly if no signer configured.
nostr_list_relaysConfigured relay pool + each relay's connection status.
nostr_query_eventsThe workhorse. NIP-01 filters: kinds, authors, e_tag / p_tag / d_tag / t_tag tag filters (mapped to NIP-01 #e/#p/#d/#t internally — renamed in v0.2.0 for hosted-API schema compatibility), since / until / limit.
nostr_get_profileFetch + parse kind:0 metadata for a pubkey or npub. Returns the parsed JSON content (name, about, picture, nip05, lud16, …).
nostr_verify_nip05Resolve name@domain → pubkey via /.well-known/nostr.json. Optional expected_pubkey for verification mode.
Write (require signer; gated by KindAllowlist + RateLimiter + optional confirm)
ToolPurpose
nostr_publish_eventThe primitive write tool. Pass kind / content / tags.
nostr_publish_text_noteConvenience for kind:1. Reply/mention/hashtag shortcuts auto-assemble into NIP-10 tags.
nostr_publish_metadataKind:0 profile. Always demands two-step confirmation regardless of NOSTR_REQUIRE_CONFIRM — overwriting your profile is hard to reason about.
nostr_publish_addressable_eventKinds 30000–39999 (replaceable). Sets the d tag automatically. The bridge marketplace-mcp uses for NIP-15.
nostr_delete_eventNIP-09 kind:5 soft delete. Best-effort — relays may ignore.
nostr_confirm_publishExecute a token-gated publish. Single-use; safety pipeline re-runs.
DMs (highest-risk; default-off via NOSTR_DM_TOOLS_ENABLED=true)
ToolPurpose
nostr_send_dmNIP-04 (kind:4) DM with NIP-44 encryption by default; NIP-04 supported for legacy compat. Gated by NOSTR_DM_ALLOWLIST.
nostr_list_dmsFetch + decrypt the thread with a counterparty. Auto-detects NIP-44 vs NIP-04 per event.
nostr_decrypt_dmDecrypt a single ciphertext (when you already have the event from elsewhere).

NIP-17 sealed/gift-wrapped DMs are not yet supported — deferred to a future v0.2 (rumor events + gift-wrapping add nontrivial complexity).


Requirements

  • Node 20+
  • A NOSTR signer — strongly preferred: a NIP-46 bunker URI from Amber (Android), nsec.app (web), or any other NIP-46 implementation. Legacy path: a raw nsec in .env. The server logs a stderr warning at startup when nsec-on-disk is detected.

Install

# From npm (once published)
npx -y nostr-ops-mcp

# From source
git clone <repo>
cd nostr-ops-mcp
corepack enable pnpm
pnpm install
pnpm build

Configure

cp .env.example .env
# edit .env: set NOSTR_NIP46_URI (recommended) OR NOSTR_PRIVATE_KEY
#           set NOSTR_RELAYS (comma-separated wss://)
#           set NOSTR_ALLOWED_KINDS (required when a signer is configured)

The server auto-loads .env from this binary's own directory (next to dist/) — deliberately NOT from cwd, to avoid env-var collision when multiple MCP servers run in the same Claude Code session.

Required
VarPurpose
NOSTR_RELAYSComma-separated wss:// relays. Server refuses to start if empty.
NOSTR_ALLOWED_KINDSComma-separated event-kind numbers the server may sign. Required when a signer is configured. Example: 1,30017,30018 for text-note + NIP-15 marketplace. Default omits kind:0 (profile) and kind:5 (delete) — both easy to misuse.
Signer — provide AT MOST one
VarPurpose
NOSTR_NIP46_URIbunker://<pubkey>?relay=...&secret=... from Amber / nsec.app / Alby Account / any NIP-46 bunker. Recommended.
NOSTR_PRIVATE_KEYRaw nsec1.... Dev/legacy only. Server warns at startup.
Optional safety knobs
VarDefaultPurpose
NOSTR_READ_ONLYfalseForce read-only — disables all write tools.
NOSTR_DM_TOOLS_ENABLEDfalseOpt-in for send_dm / list_dms / decrypt_dm.
NOSTR_DM_ALLOWLISTunsetHex pubkeys allowed as DM recipients. Empty = NOSTR_DM_TOOLS_ENABLED alone gates.
NOSTR_REQUIRE_CONFIRMfalseTwo-step confirm: write tools return a token, nostr_confirm_publish executes.
NOSTR_MAX_EVENTS_PER_MINUTE10Rolling 60s rate limit on writes.
NOSTR_MAX_DMS_PER_MINUTE5Same but for DMs.
NOSTR_ALLOW_NSEC_DECODEfalseAllow nostr_decode to return raw private key material. Don't enable unless you really need it.
NOSTR_LOG_PATH./nostr-mcp.logServer log path.
NOSTR_AUDIT_PATH./nostr-mcp-audit.logStructured audit log (one JSON line per tool call).

Wire into an MCP client

Claude Code (project-scoped)
claude mcp add nostr-ops -s project node "$(pwd)/dist/index.js"
Claude Desktop / Cursor / other clients
{
  "mcpServers": {
    "nostr-ops": {
      "command": "npx",
      "args": ["-y", "nostr-ops-mcp"],
      "env": {}
    }
  }
}

Because the server loads its own .env, leave the env block empty in the client config — keep secrets out of any committed file.


Safety model

Every write tool runs the pipeline in this order:

  1. NOSTR_READ_ONLY gate — refuse outright.
  2. Signer presence — refuse if neither nsec nor NIP-46 URI is configured.
  3. KindAllowlist — refuse if the event kind isn't in NOSTR_ALLOWED_KINDS.
  4. RateLimiter — refuse if the rolling 60s events bucket is full.
  5. Confirm gate — if NOSTR_REQUIRE_CONFIRM=true (or the tool always-confirms, like publish_metadata), return a 16-byte hex token instead of signing.
  6. Sign + publish — via NDK; the signer handshake completes lazily on first use (relevant for NIP-46 where the bunker handshake is async).
  7. Audit log — append-only JSON line for every attempt (ok / blocked / error).

DM tools add three more checks on top: NOSTR_DM_TOOLS_ENABLED, DmAllowlist (per-recipient), and a separate dms rate bucket.

The floor is your signer. If using NIP-46, the bunker can refuse any sign request — that's the strongest safety boundary. This server's checks are belt-and-suspenders on top.

Verifying calls actually went through
tail -n 5 nostr-mcp-audit.log

Successful publish: {"ts":"...","tool":"nostr_publish_text_note","outcome":"ok","result":{"event_id":"...","relays_accepted":[...]}}. Blocked / error lines are equally structured. The audit log is append-only by intent — rotate it as part of your operational hygiene.


Testing

pnpm typecheck   # tsc --noEmit
pnpm test        # 13 vitest cases (KindAllowlist, RateLimiter, nip19 roundtrip)
pnpm build       # dist/index.js (~58 KB ESM bundle)

For end-to-end testing against live relays, configure a throwaway nsec + a couple of public relays (damus.io, nos.lol) and run a small loop: nostr_publish_text_note → nostr_query_events to confirm the note round-tripped. The nostr_send_dm → nostr_list_dms loop validates the DM path (you can DM yourself for a closed-loop check).


Companion servers

  • nwc-mcp — Lightning wallet over NWC. Pair these to build sats-spending NOSTR agents.
  • marketplace-mcp — NIP-15 marketplace publish (Shopstr-compatible). Uses the same signer setup as this server.

License

MIT — see LICENSE.

Contact / Issues

Built by LLMOps.Pro.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.