Lightning-gated MCP server for Nostr signing, publishing, and verifiable agent actions. Pay per call in sats.
Endpoint: https://mcp.jorgenclaw.ai/mcp
Transport: Streamable HTTP (MCP 2025-03-26)No API key. No account. Pay each tool call with a Lightning invoice.
Related MCP server: Nostr Tools for AI Agents
Tool | Description | Price |
| Fetch a Nostr profile by npub or hex pubkey | 5 sats |
| Fetch recent notes by author or hashtag | 5 sats |
| Create a Lightning invoice | 5 sats |
| Verify an action receipt by event ID | 5 sats |
| Sign a Nostr event using Jorgenclaw's signing daemon | 21 sats |
| Sign and publish an event to relays | 21 sats |
| Post a kind 1 text note (sign + publish) | 21 sats |
| Create a signed action receipt (kind 1111) attesting an agent's action | 21 sats |
| Zap a Nostr user via Lightning (+ zap amount, max 5000 sats) | 50 sats |
Pricing tiers: 5 sats (reads), 21 sats (signing/publishing), 50 sats (zaps).
Pay per call. No server. No domain. No 3am restarts. Cheaper than self-hosting for most users.
Call any tool — the server responds with a Lightning invoice
Pay the invoice (any Lightning wallet)
Send the payment_preimage from the payment back to the tool
The server executes the action and returns the result
All signing goes through a dedicated signing daemon. The private key never enters the MCP server process.
The create_action_receipt tool produces a signed kind 1111 Nostr event that serves as third-party attestation of an agent's action. This gives agents a verifiable audit trail — any Nostr client can independently verify the receipt was signed by Jorgenclaw's key.
Signing daemon — holds the nsec in kernel memory, exposes signing via Unix socket
MCP server — stateless, handles tool calls and Lightning payment flow
NWC (NIP-47) — invoice generation and payment verification via Nostr Wallet Connect
Cloudflare Tunnel — HTTPS termination, no exposed ports
Pubkey: d0514175a31de1942812597ee4e3f478b183f7f35fb73ee66d8c9f57485544e4
NIP-05: jorgenclaw@jorgenclaw.ai
Website: jorgenclaw.ai
nostr-mcp-server — Free Nostr MCP server (23 tools, open source)
NanoClaw — Agent framework powering Jorgenclaw
Proprietary — the server is hosted, not distributed.
Create a signed action receipt (kind 1111) attesting an agent's action. Third-party attestation via Jorgenclaw's signing key. Price: 21 sats.
Inputs: agent_id (required), action (required), summary (required), metadata, +1 more.
Create a Lightning invoice. Price: 5 sat.
Inputs: amount_sats (required), description, payment_preimage.
Fetch a Nostr profile (kind 0) by npub or hex pubkey. Price: 5 sat.
Inputs: pubkey (required), payment_preimage.
Fetch recent kind 1 notes by author or hashtag. Price: 5 sats.
Inputs: author, hashtag, limit, payment_preimage.
Post a kind 1 text note to Nostr (sign + publish in one call). Price: 21 sats.
Inputs: content (required), tags, payment_preimage.
Sign and publish a Nostr event to relays. Price: 3 sats.
Inputs: kind (required), content (required), tags, created_at, +2 more.
Sign a Nostr event using a sovereign signing daemon. Price: 2 sats.
Inputs: kind (required), content (required), tags, created_at, +1 more.
Zap a Nostr user via Lightning. Price: 50 sats (tool fee) + zap amount. Max 5000 sats.
Inputs: npub (required), amount_sats (required), comment, payment_preimage.
Verify an action receipt by event ID. Confirms it was signed by Jorgenclaw's key. Price: 5 sat.
Inputs: event_id (required), payment_preimage.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 9 tools
Most tools have distinct purposes, such as nostr_fetch_profile for retrieving profiles and nostr_zap for sending payments. However, nostr_post_note and nostr_publish_event have some overlap in publishing Nostr events, which could cause minor confusion, though their descriptions differentiate them slightly (post_note is specifically for kind 1 notes, while publish_event is general).
Tool names follow a consistent snake_case pattern with clear verb_noun structures, such as create_action_receipt and nostr_fetch_profile. All tools adhere to this convention, making them predictable and easy to parse, with no mixing of styles or deviations.
With 9 tools, the count is well-scoped for a server focused on Nostr and Lightning operations. Each tool serves a specific function in this domain, such as fetching data, posting content, or handling payments, without feeling excessive or insufficient for the intended purpose.
The tool set covers key Nostr and Lightning workflows, including profile fetching, note posting, zapping, and receipt handling. A minor gap is the lack of tools for managing relays or handling other Nostr event kinds beyond basics, but agents can work around this with the provided tools for core operations.
Agent registry with Nostr identity, reputation, escrow, observability, and Lightning payments.
Pay-per-action access to APIs and MCP tools over Lightning L402 and Base USDC x402.
Verified, pay-per-use API tools for AI agents through one authenticated connection.
10 pay-per-call tools for AI agents: QR, screenshots, DNS, OCR, PDF, email & more. USDC on Base.